# CVE-2012-2760: Information disclosure in n/a

> Local attackers can read world-readable OpenID session files to steal session IDs and potentially hijack user accounts.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2760, GHSA-4m35-7rw5-2cp2

## What is CVE-2012-2760?

CVE-2012-2760 is a low-severity vulnerability in n/a, published on 25 Jul 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

mod_auth_openid before 0.7 for Apache uses world-readable permissions for /tmp/mod_auth_openid.db, which allows local users to obtain session ids.

Weakness: CWE-264

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

It affects 1 product.


Products: Findingscience Mod Auth Openid.

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

Upgrade to a fixed version.

## Is CVE-2012-2760 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-2760 exists.

Public exploit code:

- Apache Mod_Auth_OpenID - Session Stealing (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2760 is a low-severity vulnerability in n/a, published on 25 Jul 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-2760 exists.

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-2760/ (Markdown: https://insights.sbomify.com/CVE-2012-2760/index.md)
```

## Sources

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

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