CVE-2020-7787
Description
This affects all versions of package react-adal. It is possible for a specially crafted JWT token and request URL can cause the nonce, session and refresh values to be incorrectly validated, causing the application to treat an attacker-generated JWT token as authentic. The logical defect is caused by how the nonce, session and refresh values are stored in the browser local storage or session storage. Each key is automatically appended by ||. When the received nonce and session keys are generated, the list of values is stored in the browser storage, separated by ||, with || always appended to the end of the list. Since || will always be the last 2 characters of the stored values, an empty string ("") will always be in the list of the valid values. Therefore, if an empty session parameter is provided in the callback URL, and a specially-crafted JWT token contains an nonce value of "" (empty string), then adal.js will consider the JWT token as authentic.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
react-adalnpm | < 0.5.1 | 0.5.1 |
Affected products
2- react-adal/react-adaldescription
Patches
Vulnerability mechanics
References
5- github.com/salvoravida/react-adal/pull/115nvdExploitThird Party AdvisoryWEB
- snyk.io/vuln/SNYK-JS-REACTADAL-1018907nvdExploitThird Party AdvisoryWEB
- github.com/advisories/GHSA-7mpx-vg3c-cmr4ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2020-7787ghsaADVISORY
- github.com/salvoravida/react-adal/commit/74158dba1647b12fe96fa401e306a6287fe9e2a9ghsaWEB
News mentions
0No linked articles in our index yet.