# GHSA-5v7r-jg9r-vq44: Insecure Cryptography Algorithm in simple-crypto-js

> Attackers can break encryption and access sensitive data due to insecure AES-CBC implementation in simple-crypto-js.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-5v7r-jg9r-vq44?

GHSA-5v7r-jg9r-vq44 is a vulnerability in simple-crypto-js, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-5v7r-jg9r-vq44?

2 open source packages ship an affected version, including simple-crypto-js.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `simple-crypto-js` | npm | All versions | 2.3.0 |
| `simple-crypto-js` | npm | All versions | 2.3.0 |

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

Upgrade simple-crypto-js to 2.3.0 or later.

## Is GHSA-5v7r-jg9r-vq44 being exploited?

There is no known exploitation of GHSA-5v7r-jg9r-vq44 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5v7r-jg9r-vq44 and fix it if it is affected.

What it is: GHSA-5v7r-jg9r-vq44 is a vulnerability in simple-crypto-js, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-5v7r-jg9r-vq44 in the wild and no public exploit code.

Affected packages and fixed versions:
- simple-crypto-js (npm): affected all versions; fixed in 2.3.0
- simple-crypto-js (npm): affected all versions; fixed in 2.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-5v7r-jg9r-vq44/ (Markdown: https://insights.sbomify.com/GHSA-5v7r-jg9r-vq44/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5v7r-jg9r-vq44

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5v7r-jg9r-vq44/
Summaries are generated and may contain mistakes; the official description above is the record.