dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-46947

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Northern.tech Mender before 3.6.6 and 3.7.x before 3.7.7 allows SSRF.

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 · moderate confidence

Mender IoT device management software before versions 3.6.6 and 3.7.7 contains a Server-Side Request Forgery (SSRF) vulnerability that allows attackers to induce the application to make HTTP requests to arbitrary destinations, potentially accessing internal services or exfiltrating data.

MitigationUpgrade Mender to version 3.6.6 or 3.7.7 or later to remediate the SSRF vulnerability. If immediate patching is not possible, implement network segmentation and restrict outbound access from the Mender server.

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

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 installed Mender version
    Access the Mender UI and navigate to the About or Settings page to view the server version. Alternatively, query the Mender API endpoint /api/management/v1/server/version or use the CLI command 'mender --version' if available.
    Affected if The version displayed is earlier than 3.6.6 or earlier than 3.7.7 (note: Mender has multiple release tracks; either condition indicates vulnerability).
  2. Confirm Mender Server component is deployed
    Check if the Mender Server service is running in your environment. This can be done by querying the running containers (e.g., 'docker ps' or 'kubectl get pods') for mender-api-gateway, mender-deployments, mender-inventory, or similar Mender backend services.
    Affected if Mender Server components are running and the version from step 1 is unpatched.
  3. Identify web-facing integration features
    Review Mender configuration files (commonly in /etc/mender or within the docker-compose/kubernetes deployment manifests) for enabled integration modules such as webhooks, external artifact storage connectors, or third-party IoT platform integrations that may trigger outbound HTTP requests.
    Affected if Any integration feature that can initiate outbound HTTP requests from the Mender Server is configured and the server version is unpatched.
  4. Audit recent HTTP outbound requests
    Examine Mender Server logs (typically accessed via 'docker logs' or kubectl logs) for the mender-api-gateway or related services, focusing on outbound HTTP requests. Look for unexpected internal IP addresses or suspicious target domains in request patterns.
    Affected if Outbound requests from Mender Server have originated to internal services, localhost, or unexpected external destinations, and the server version is unpatched.

You are affected if your Mender Server version is earlier than 3.6.6 or 3.7.7, and the server has integration features enabled that can trigger outbound HTTP requests.

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 to version 3.6.6 or 3.7.7 or later to remediate the SSRF vulnerability. If immediate patching is not possible, implement network segmentation and restrict outbound access from the Mender server.

Recommended fix High confidence

Mender 3.6.6 or later / Mender 3.7.7 or later (depending on your current branch)

  1. 1. Identify the currently installed Mender version by checking the Mender server or artifact version
  2. 2. For Mender 3.6.x versions: upgrade to Mender 3.6.6 or later (preferably the latest 3.6.x stable release)
  3. 3. For Mender 3.7.x versions: upgrade to Mender 3.7.7 or later (preferably the latest 3.7.x stable release)
  4. 4. Consult the official Mender upgrade documentation for your deployment type (on-premise, hosted, or embedded device)
  5. 5. Before production deployment, test the upgrade in a staging environment to verify compatibility with your specific Mender setup
  6. 6. After upgrade, verify the SSRF vulnerability is resolved by confirming the patched version is running

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-46947 — 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-2024-46947 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