# CVE-2011-3267: Denial of service in n/a

> Attackers can crash PHP applications via the error_log function, causing 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 stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 25 Aug 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vc8p-pj3m-8xpw

## What is CVE-2011-3267?

CVE-2011-3267 is a medium-severity denial of service vulnerability in Php Php, published on 25 Aug 2011. 

### Official description

PHP before 5.3.7 does not properly implement the error_log function, which allows context-dependent attackers to cause a denial of service (application crash) via unspecified vectors.

Weakness: CWE-399

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

It affects 1 product.


Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2011-3267 being exploited?

There is no known exploitation of CVE-2011-3267 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-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3267 is a medium-severity denial of service vulnerability in Php Php, published on 25 Aug 2011. 
Exploitation: There is no known exploitation of CVE-2011-3267 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-3267/ (Markdown: https://insights.sbomify.com/CVE-2011-3267/index.md)
```

## Sources

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

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