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

> Remote attackers can modify user public keys via mass assignment, potentially leading to privilege escalation or unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 4 Apr 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8qp2-79w8-8586

## What is CVE-2012-2055?

CVE-2012-2055 is a high-severity missing authorization vulnerability in n/a, published on 4 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GitHub Enterprise before 20120304 does not properly restrict the use of a hash to provide values for a model's attributes, which allows remote attackers to set the public_key[user_id] value via a modified URL for the public-key update form, related to a "mass assignment" vulnerability.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources)

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

It affects 1 product.


Products: Github Github.

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

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

## Is CVE-2012-2055 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10516](https://insights.sbomify.com/CVE-2020-10516/): Improper access control in GitHub Enterprise Server leading to privilege escalation of organization member (critical 9.8)
- [CVE-2017-18365](https://insights.sbomify.com/CVE-2017-18365/): Deserialization in n/a (critical 9.8)
- [CVE-2020-10519](https://insights.sbomify.com/CVE-2020-10519/): Unsafe configuration options in GitHub Pages leading to remote code execution on GitHub Enterprise Server (high 8.8)
- [CVE-2020-10518](https://insights.sbomify.com/CVE-2020-10518/): Unsafe configuration options in GitHub Pages leading to remote code execution on GitHub Enterprise Server (high 8.8)
- [CVE-2021-22863](https://insights.sbomify.com/CVE-2021-22863/): Missing authorization in GitHub Enterprise Server (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2055 is a high-severity missing authorization vulnerability in n/a, published on 4 Apr 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-2055 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-2055/ (Markdown: https://insights.sbomify.com/CVE-2012-2055/index.md)
```

## Sources

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

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