dbcve.org
SignedxmlApplication · Moov

CVE-2023-34205

CRITICAL · 9.1 CVSS v3.1 Published 2023-05-30
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
In Moov signedxml through 1.0.0, parsing the raw XML (as received) can result in different output than parsing the canonicalized XML. Thus, signature validation can be bypassed via a Signature Wrapping attack (aka XSW).

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 Moov signedxml library versions through 1.0.0 fails to properly canonicalize XML before signature validation. When raw XML (as received) is parsed versus canonicalized XML, different outputs result. This allows an attacker to perform a Signature Wrapping (XSW) attack by modifying the XML structure after signing while the signature still appears valid.

MitigationUpgrade signedxml to a version beyond 1.0.0 that implements proper XML canonicalization (C14N) before signature validation to ensure the signed content matches the validated content.

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
SignedxmlApplication
Affected:= 1.0.0

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
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Check signedxml version in use
    Run 'go list -m all | grep signedxml' or inspect your go.mod file for 'github.com/moov-io/signedxml'
    Affected if The version listed is 1.0.0 exactly
  2. Verify XML signature validation is performed
    Search codebase for usage of SignedXML, Verify, or signature-related functions from the signedxml package
    Affected if The application uses signedxml to validate XML signatures from external or untrusted sources
  3. Confirm XML content comes from external sources
    Review code paths where XML is received over network, uploaded, or parsed from user-controlled data
    Affected if The validated XML originates from outside the application or from untrusted input
  4. Check for C14N canonicalization in signature workflow
    Inspect the signedxml verification code path to see if Canonicalize or EnvelopedSignature transform is applied before signature validation
    Affected if No explicit canonicalization is performed prior to signature verification (raw XML is validated as-is)

You are affected if using signedxml version 1.0.0 to validate XML signatures from untrusted sources without applying explicit C14N canonicalization beforehand.

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 signedxml to a version beyond 1.0.0 that implements proper XML canonicalization (C14N) before signature validation to ensure the signed content matches the validated content.

Recommended fix Moderate confidence

Latest patched version (check github.com/moov-io/signedxml releases for version after 1.0.0)

  1. Check your project's go.mod file to confirm you are using signedxml version 1.0.0 or a vulnerable earlier version
  2. Run 'go get github.com/moov-io/signedxml@latest' to fetch the latest version
  3. Run 'go mod tidy' to update dependencies
  4. Verify the upgrade by checking 'go list -m all' or reviewing go.mod to confirm the new signedxml version
  5. Rebuild and test your application to ensure the signature verification fix is working correctly
Caveat Review release notes for any breaking changes between 1.0.0 and the patched version

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

Fix this in Signedxml Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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