Authentication Bypass in saml2-js

published 2020-09-03 6y ago modified 2021-09-29 5y ago

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

Versions of `saml2-js` prior to 2.0.5 are vulnerable to an Authentication Bypass. The package fails to enforce the assertion conditions for encrypted assertions, which may allow an attacker to reuse encrypted assertion tokens indefinitely.

## Recommendation

Upgrade to version 2.0.5 or later.

Patch / fix

fixed in 1 links 2

npm saml2-js 2.0.5

github.com/Clever/saml2@ae0da4d commit
github.com/Clever/saml2#190 pull request

Is GHSA-mfcp-34xw-p57x 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

CVSS scores

assigned by	version	score	vector
GitHub	3.1	6.8	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	saml2-js	<2.0.5	2.0.5

Classification

Weakness

CWE-287 Improper Authentication

References

Sources

GitHub Advisory GHSA-mfcp-34xw-p57x

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.