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

CVE-2024-34581

HIGH · 7.3 CVSS v3.1 Published 2024-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 W3C XML Signature Syntax and Processing (XMLDsig) specification, starting with 1.0, was originally published with a "RetrievalMethod is a URI ... that may be used to obtain key and/or certificate information" statement and no accompanying information about SSRF risks, and this may have contributed to vulnerable implementations such as those discussed in CVE-2023-36661 and CVE-2024-21893. NOTE: this was mitigated in 1.1 and 2.0 via a directly referenced Best Practices document that calls on implementers to be wary of 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 · high confidence

The XMLDsig 1.0 specification allowed RetrievalMethod URIs to fetch remote key/certificate resources without SSRF warnings, leading to vulnerable implementations that can be coerced into making arbitrary HTTP requests. This design flaw was addressed in XMLDsig 1.1 and 2.0 via a Best Practices document requiring SSRF protections.

MitigationUpdate XMLDsig implementations to version 1.1 or 2.0, or implement explicit SSRF protections (allowlists, request size limits, timeout enforcement) around RetrievalMethod URI processing.

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

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

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 XMLDsig implementation in use
    Search your codebase, dependencies, or application for XMLDsig, XML Digital Signature, or related XML signature libraries (e.g., Apache Santuario, Python lxml, Java XML Digital Signature API)
    Affected if An XMLDsig library or module is present and processes XML documents with digital signatures
  2. Determine the XMLDsig version
    Check the version of the XMLDsig library or verify which specification version (1.0, 1.1, or 2.0) is implemented. Consult library documentation or inspect package metadata
    Affected if The implementation is based on XMLDsig 1.0 specification without SSRF protections
  3. Inspect for RetrievalMethod element usage
    Review XML documents or signature payloads processed by your application for <RetrievalMethod> elements, particularly those with URI attributes pointing to http:// or https:// URLs
    Affected if Your application processes XML signatures containing RetrievalMethod URIs that reference remote resources
  4. Verify SSRF protections on URI processing
    Inspect code that handles RetrievalMethod URI fetching. Look for allowlists, deny-lists, timeout settings, or request size limits applied to external URI resolution
    Affected if No explicit SSRF protections (allowlists, timeouts, size limits) are implemented around RetrievalMethod URI fetching
  5. Check for external HTTP requests during signature verification
    Monitor network traffic or review logs when your application verifies XML signatures. Look for outgoing HTTP/HTTPS requests triggered by signature validation
    Affected if Signature verification causes arbitrary HTTP requests to external URIs without validation

Your environment is affected if you use an XMLDsig 1.0 implementation that processes RetrievalMethod URIs without explicit SSRF protections, allowing the library to fetch remote key or certificate resources from arbitrary URLs.

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

Update XMLDsig implementations to version 1.1 or 2.0, or implement explicit SSRF protections (allowlists, request size limits, timeout enforcement) around RetrievalMethod URI processing.

Recommended fix Moderate confidence

XMLDsig 1.1 or XMLDsig 2.0 specification

  1. Ensure XMLDsig implementations follow the Best Practices document referenced in XMLDsig 1.1 and 2.0 specifications to mitigate SSRF risks
  2. Review the XMLDsig 1.1 or 2.0 specification and implement the SSRF mitigation guidance provided in the Best Practices document
  3. For existing implementations using XMLDsig 1.0, audit RetrievalMethod usage to prevent uncontrolled URI resolution that could lead to SSRF
  4. Consider migrating to XMLDsig 1.1 or 2.0 which include explicit SSRF warnings in the specification
Caveat Minimal; primarily involves following security best practices in the specification. Migration from XMLDsig 1.0 should be straightforward as 1.1/2.0 are backward compatible for most use cases.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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