# CVE-2011-3268: Memory corruption in n/a

> A buffer overflow in PHP's crypt function allows attackers to cause unspecified impacts via a long salt argument.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 25 Aug 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r34w-4wfm-896r

## What is CVE-2011-3268?

CVE-2011-3268 is a critical memory corruption vulnerability in Php Php, published on 25 Aug 2011. 

### Official description

Buffer overflow in the crypt function in PHP before 5.3.7 allows context-dependent attackers to have an unspecified impact via a long salt argument, a different vulnerability than CVE-2011-2483.

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

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

It affects 1 product.


Products: Php Php.

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

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

## Is CVE-2011-3268 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-2050](https://insights.sbomify.com/CVE-2008-2050/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3268 is a critical memory corruption vulnerability in Php Php, published on 25 Aug 2011. 
Exploitation: There is no known exploitation of CVE-2011-3268 in the wild and no public exploit code.

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

## Sources

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

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