Skip to content

GO-2022-0409

An attacker can create an XML file which completely bypasses signature validation, passing off an altered file as a signed one.

Not rated yet Withdrawn May 15, 2024 Go
Severity
Not rated yet
No source has published a CVSS score yet
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
—
Not classified
Fix
1.1.0
Upgrade github.com/russellhaering/goxmldsig to this version or later

Description

An attacker can create an XML file which completely bypasses signature validation, passing off an altered file as a signed one.

Affected versions

Go

PackageVulnerableFixed in
github.com/russellhaering/goxmldsig
< 1.1.0
1.1.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/russellhaering/goxmldsig Go → 1.1.0

go
go get github.com/russellhaering/goxmldsig@v1.1.0 && go mod tidy

References

Timeline

  1. Published
  2. Withdrawn
AdvisorySeverityWhy it's related
GHSA-479m-364c-43vc
validateSignature Loop Variable Capture Signature Bypass in goxmldsig
High Also affects github.com/russellhaering/goxmldsig
GHSA-rrfw-hg9m-j47h
Signature Validation Bypass
Critical Also affects github.com/russellhaering/goxmldsig
GHSA-q547-gmf8-8jr7
github.com/russellhaering/goxmldsig vulnerable to Signature Validation Bypass
Medium Also affects github.com/russellhaering/goxmldsig
GHSA-mqqv-chpx-vq25
Duplicate Advisory: gosaml2 is vulnerable to NULL Pointer Dereference from malformed XML signatures
High Also affects github.com/russellhaering/goxmldsig
GHSA-m9hp-7r99-94h5
Authentication Bypass in dex
Critical Also affects github.com/russellhaering/goxmldsig
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor