# CVE-2012-2455: Auth bypass in n/a

> Remote attackers can bypass authentication to read or modify user, customer, and project data due to missing registration ID validation.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 10 Nov 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4hgj-q2x7-8h69

## What is CVE-2012-2455?

CVE-2012-2455 is a medium-severity authentication bypass vulnerability in n/a, published on 10 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Advanced Productivity Software DTE Axiom before 12.3.3 does not validate the registration ID, which allows remote attackers to bypass authentication and read or modify data about users, customers, and projects via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Advance Productivity Software Dte Axiom.

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

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

## Is CVE-2012-2455 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2455 is a medium-severity authentication bypass vulnerability in n/a, published on 10 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-2455 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-2455/ (Markdown: https://insights.sbomify.com/CVE-2012-2455/index.md)
```

## Sources

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

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