# CVE-2012-2317: Auth bypass in n/a

> Remote attackers can bypass authentication in applications using PHP crypt with empty salts due to improper handling in Debian/Ubuntu patches.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** 7 Aug 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qcwp-wm5p-xc8j

## What is CVE-2012-2317?

CVE-2012-2317 is a medium-severity authentication bypass vulnerability in Canonical Ubuntu Linux, published on 7 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Debian php_crypt_revamped.patch patch for PHP 5.3.x, as used in the php5 package before 5.3.3-7+squeeze4 in Debian GNU/Linux squeeze, the php5 package before 5.3.2-1ubuntu4.17 in Ubuntu 10.04 LTS, and the php5 package before 5.3.5-1ubuntu7.10 in Ubuntu 11.04, does not properly handle an empty salt string, which might allow remote attackers to bypass authentication by leveraging an application that relies on the PHP crypt function to choose a salt for password hashing.

Weakness: CWE-310

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

It affects 4 products.


Products: Canonical Php5, Canonical Ubuntu Linux, Debian Debian Linux, Debian Php5-Common.

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

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

## Is CVE-2012-2317 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2317 is a medium-severity authentication bypass vulnerability in Canonical Ubuntu Linux, published on 7 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-2317 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2317/ (Markdown: https://insights.sbomify.com/CVE-2012-2317/index.md)
```

## Sources

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

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