dbcve.org
MenderApplication · Northern.tech

CVE-2022-29556

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The iot-manager microservice 1.0.0 in Northern.tech Mender Enterprise before 3.2.2 allows SSRF because the Azure IoT Hub integration provides several SSRF primitives that can execute cross-tenant actions via internal API endpoints.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The iot-manager microservice 1.0.0 in Mender Enterprise contains an SSRF vulnerability in the Azure IoT Hub integration. The integration exposes SSRF primitives that allow attackers to make the service issue requests to internal API endpoints, potentially enabling cross-tenant actions and unauthorized access to internal resources.

MitigationUpgrade Mender Enterprise to version 3.2.2 or later to patch the vulnerable iot-manager microservice. Additionally, restrict network access to internal API endpoints and implement strict allowlists for the Azure IoT Hub integration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MenderApplication
Affected:= 3.2.0= 3.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mender Enterprise version
    Locate the Mender Enterprise installation and retrieve its version number. This is typically visible in the product UI, API, or deployment configuration files.
    Affected if The installed version is 3.2.0 or 3.2.1 specifically.
  2. Locate the iot-manager microservice
    Find the iot-manager microservice in the Mender Enterprise deployment. Check its version or build metadata, which typically shows version 1.0.0 for the affected release.
    Affected if The iot-manager microservice version is 1.0.0 running on Mender versions 3.2.0 or 3.2.1.
  3. Verify Azure IoT Hub integration is configured
    Inspect the Mender configuration or integration settings to determine if the Azure IoT Hub integration module is enabled or has been configured.
    Affected if The Azure IoT Hub integration is enabled or has been configured in the affected Mender versions.
  4. Check for internal network request capability
    Review network logs or audit trails from the iot-manager service to identify any suspicious outbound requests to internal or non-public API endpoints.

A user is affected if they are running Mender Enterprise versions 3.2.0 or 3.2.1 with the Azure IoT Hub integration enabled and the iot-manager microservice present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Mender Enterprise to version 3.2.2 or later to patch the vulnerable iot-manager microservice. Additionally, restrict network access to internal API endpoints and implement strict allowlists for the Azure IoT Hub integration.

Recommended fix High confidence

Mender Enterprise 3.2.2

  1. 1. Back up your current Mender Enterprise configuration and database
  2. 2. Update your Mender Enterprise installation to version 3.2.2 or later
  3. 3. Verify the iot-manager microservice has been updated to a version that includes the SSRF fix
  4. 4. Test the Azure IoT Hub integration to confirm functionality works as expected after the update
  5. 5. Review audit logs to ensure no unauthorized cross-tenant access occurred during the vulnerable period

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mender Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29556 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data