# CVE-2012-4022: Denial of service in n/a

> Remote attackers can cause loss of blog-entry viewability in Pebble via crafted comments, requiring an upgrade to fix.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 8 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5prv-rg9r-4whf

## What is CVE-2012-4022?

CVE-2012-4022 is a medium-severity denial of service vulnerability in n/a, published on 8 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pebble before 2.6.4 allows remote attackers to trigger loss of blog-entry viewability via a crafted comment.

Weakness: CWE-264

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

It affects 1 product.


Products: Simon Brown Pebble.

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

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

## Is CVE-2012-4022 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5170](https://insights.sbomify.com/CVE-2012-5170/): Open redirect in n/a (medium 5.8)
- [CVE-2012-4023](https://insights.sbomify.com/CVE-2012-4023/): Other in n/a (medium 4.3)
- [CVE-2009-0736](https://insights.sbomify.com/CVE-2009-0736/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2006-5168](https://insights.sbomify.com/CVE-2006-5168/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4022 is a medium-severity denial of service vulnerability in n/a, published on 8 Nov 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-4022 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-4022/ (Markdown: https://insights.sbomify.com/CVE-2012-4022/index.md)
```

## Sources

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

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