# CVE-2012-2092: Security feature bypass in Cobbler

> An error in GPG signature verification allows attackers to bypass security checks in the Ubuntu Cobbler import script.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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:** 6 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vgq2-gxqp-v52x

## What is CVE-2012-2092?

CVE-2012-2092 is a medium-severity vulnerability in Ubuntu Cobbler, published on 6 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Security Bypass vulnerability exists in Ubuntu Cobbler before 2,2,2 in the cobbler-ubuntu-import script due to an error when verifying the GPG signature.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 1 product.


Products: Canonical Ubuntu Cobbler.

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

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

## Is CVE-2012-2092 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2092 is a medium-severity vulnerability in Ubuntu Cobbler, published on 6 Dec 2019. 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-2092 in the wild and no public exploit code.

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

## Sources

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

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