# CVE-2012-3367: Missing authorization in n/a

> Attackers with revocation permissions can improperly revoke CA certificates, compromising the certificate authority's integrity and availability.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jh3f-4cfw-pgf7

## What is CVE-2012-3367?

CVE-2012-3367 is a medium-severity missing authorization vulnerability in n/a, published on 13 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Red Hat Certificate System (RHCS) before 8.1.1 and Dogtag Certificate System does not properly check certificate revocation requests made through the web interface, which allows remote attackers with permissions to revoke end entity certificates to revoke the Certificate Authority (CA) certificate.

Weakness: CWE-310

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

It affects 2 products.


Products: Redhat Certificate System, Redhat Dogtag Certificate System.

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

Upgrade to a fixed version.

## Is CVE-2012-3367 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1886](https://insights.sbomify.com/CVE-2013-1886/): Other in n/a (high 7.5)
- [CVE-2009-0588](https://insights.sbomify.com/CVE-2009-0588/): Missing authorization in n/a (medium 6.5)
- [CVE-2010-3868](https://insights.sbomify.com/CVE-2010-3868/): Missing authorization in n/a (medium 5.8)
- [CVE-2013-1885](https://insights.sbomify.com/CVE-2013-1885/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-4543](https://insights.sbomify.com/CVE-2012-4543/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3367 is a medium-severity missing authorization vulnerability in n/a, published on 13 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-3367 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-3367/ (Markdown: https://insights.sbomify.com/CVE-2012-3367/index.md)
```

## Sources

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

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