# CVE-2011-3597: Code injection in n/a

> Attackers can execute arbitrary commands via the new constructor in the Perl Digest module, posing a risk to applications using this library.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-3597, GHSA-42c5-x389-m7vp

## What is CVE-2011-3597?

CVE-2011-3597 is a high-severity code injection vulnerability in n/a, published on 13 Jan 2012. 

### Official description

Eval injection vulnerability in the Digest module before 1.17 for Perl allows context-dependent attackers to execute arbitrary commands via the new constructor.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-3597?

It affects 1 product.


Products: Gisle Aas Digest.

## How do I fix CVE-2011-3597?

Upgrade to a fixed version.

## Is CVE-2011-3597 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-3597 exists.

Public exploit code:

- Perl 5.x - Digest Module 'Digest->new()' Code Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3597 and fix it if it is affected.

What it is: CVE-2011-3597 is a high-severity code injection vulnerability in n/a, published on 13 Jan 2012. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-3597 exists.

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

## Sources

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

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