# CVE-2012-3009: Privilege escalation in n/a

> Remote authenticated users can escalate privileges to obtain database administrative access in Siemens COMOS.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jj22-cwv6-836v

## What is CVE-2012-3009?

CVE-2012-3009 is a high-severity vulnerability in n/a, published on 16 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Siemens COMOS before 9.1 Patch 413, 9.2 before Update 03 Patch 023, and 10.0 before Patch 005 allows remote authenticated users to obtain database administrative access via unspecified method calls.

Weakness: CWE-264

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

It affects 1 product.


Products: Siemens Comos.

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

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

## Is CVE-2012-3009 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-24482](https://insights.sbomify.com/CVE-2023-24482/): Memory corruption in COMOS V10.2 (critical 10.0)
- [CVE-2023-43504](https://insights.sbomify.com/CVE-2023-43504/): Memory corruption in COMOS (critical 9.6)
- [CVE-2023-43505](https://insights.sbomify.com/CVE-2023-43505/): Missing authorization in COMOS (critical 9.6)
- [CVE-2023-46601](https://insights.sbomify.com/CVE-2023-46601/): Missing authorization in COMOS (critical 9.6)
- [CVE-2021-37197](https://insights.sbomify.com/CVE-2021-37197/): SQL injection in COMOS V10.2 (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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