# CVE-2012-3501: Command injection in n/a

> Remote attackers can crash the SquidClamav daemon by sending URLs with specific characters, causing a denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-88mf-3qc6-6m7p

## What is CVE-2012-3501?

CVE-2012-3501 is a medium-severity command injection vulnerability in n/a, published on 25 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The squidclamav_check_preview_handler function in squidclamav.c in SquidClamav 5.x before 5.8 and 6.x before 6.7 passes an unescaped URL to a system command call, which allows remote attackers to cause a denial of service (daemon crash) via a URL with certain characters, as demonstrated using %0D or %0A.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2012-3501?

It affects 1 product.


Products: Darold Squidclamav.

## How do I fix CVE-2012-3501?

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

## Is CVE-2012-3501 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4667](https://insights.sbomify.com/CVE-2012-4667/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3501 and fix it if it is affected.

What it is: CVE-2012-3501 is a medium-severity command injection vulnerability in n/a, published on 25 Aug 2012. 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-2012-3501 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-2012-3501/ (Markdown: https://insights.sbomify.com/CVE-2012-3501/index.md)
```

## Sources

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

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