# CVE-2021-27211: Weak cryptography in n/a

> Steghide uses a weak 32-bit seed, allowing attackers to easily detect hidden data embedded in files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-27211, GHSA-342w-jw3g-59cj, UBUNTU-CVE-2021-27211

## What is CVE-2021-27211?

CVE-2021-27211 is a high-severity vulnerability in n/a, published on 15 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

steghide 0.5.1 relies on a certain 32-bit seed value, which makes it easier for attackers to detect hidden data.

Weakness: CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2021-27211?

It affects 1 product.


Products: Steghide Project Steghide.

## How do I fix CVE-2021-27211?

No fix has been published for CVE-2021-27211 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-27211 being exploited?

There is no known exploitation of CVE-2021-27211 in the wild and no public exploit code.

Public exploit code:

- Exploit script for CVE-2021-27211 (github_poc): https://github.com/b4shfire/stegcrack

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-27211 and fix it if it is affected.

What it is: CVE-2021-27211 is a high-severity vulnerability in n/a, published on 15 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-27211 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2021-27211/ (Markdown: https://insights.sbomify.com/CVE-2021-27211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-27211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-27211
- OSV: https://osv.dev/vulnerability/CVE-2021-27211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-27211/
Summaries are generated and may contain mistakes; the official description above is the record.