How severe is GHSA-5v7r-jg9r-vq44?

GHSA-5v7r-jg9r-vq44 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-5v7r-jg9r-vq44?

GHSA-5v7r-jg9r-vq44 affects the following packages: simple-crypto-js (npm). Ecosystems affected: npm.

How do I fix GHSA-5v7r-jg9r-vq44?

Update simple-crypto-js to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5v7r-jg9r-vq44 is resolved across your whole dependency graph.

How do I detect GHSA-5v7r-jg9r-vq44 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simple-crypto-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5v7r-jg9r-vq44 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-5v7r-jg9r-vq44 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5v7r-jg9r-vq44 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5v7r-jg9r-vq44 published, and has it been updated?

GHSA-5v7r-jg9r-vq44 was published on September 3, 2020 and was last updated on September 29, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

Insecure Cryptography Algorithm in simple-crypto-jsGHSA-5v7r-jg9r-vq44

MEDIUMFix: danang-id/simple-crypto-js#17

GHSA-5v7r-jg9r-vq44 is a medium-severity (CVSS 5.9) vulnerability in simple-crypto-js. A fix is available for simple-crypto-js — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Sep 29, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 29, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦simple-crypto-js

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Versions of simple-crypto-js prior to 2.3.0 use AES-CBC with PKCS#7 padding, which is vulnerable to padding oracle attacks. This may allow attackers to break the encryption and access sensitive data.

Recommendation

Upgrade to version 2.3.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`simple-crypto-js`	all versions	2.3.0`npm install simple-crypto-js@2.3.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simple-crypto-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update simple-crypto-js to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5v7r-jg9r-vq44 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Versions of `simple-crypto-js` prior to 2.3.0 use AES-CBC with PKCS#7 padding, which is vulnerable to padding oracle attacks. This may allow attackers to break the encryption and access sensitive data. ## Recommendation Upgrade to version 2.3.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-5v7r-jg9r-vq44 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works