xml-crypto's HMAC-SHA1 signatures can bypass validation via key confusion

published 2020-10-26 6y ago modified 2022-08-02 4y ago

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### Impact An attacker can inject an HMAC-SHA1 signature that is valid using only knowledge of the RSA public key. This allows bypassing signature validation.

### Patches Version 2.0.0 has the fix.

### Workarounds The recommendation is to upgrade. In case that is not possible remove the 'http://www.w3.org/2000/09/xmldsig#hmac-sha1' entry from SignedXml.SignatureAlgorithms.

Patch / fix

fixed in 1 links 1

npm xml-crypto 2.0.0

github.com/yaronn/xml-crypto@3d9db71 commit

Is GHSA-c27r-x354-4m68 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	xml-crypto	<2.0.0	2.0.0

Classification

Weakness

CWE-287 Improper Authentication

References

Sources

GitHub Advisory GHSA-c27r-x354-4m68
Maintainer advisory GHSA-c27r-x354-4m68

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of node-saml/xml-crypto published their own advisory on GitHub. Reviewed sources take precedence over it.