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

> Remote attackers can leak ClaimId via ClassAd requests to condor_startd, potentially gaining sensitive information and control over job execution.

- **Severity:** Medium 5.8 (`AV:N/AC:M/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:** Yes
- **Published:** 28 Sep 2012
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2012-3493, GHSA-gqg4-4wpq-c69h

## What is CVE-2012-3493?

CVE-2012-3493 is a medium-severity vulnerability in n/a, published on 28 Sep 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The command_give_request_ad function in condor_startd.V6/command.cpp Condor 7.6.x before 7.6.10 and 7.8.x before 7.8.4 allows remote attackers to obtain sensitive information, and possibly control or start arbitrary jobs, via a ClassAd request to the condor_startd port, which leaks the ClaimId.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Condor Project Condor.

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

Upgrade to a fixed version.

## Is CVE-2012-3493 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5390](https://insights.sbomify.com/CVE-2012-5390/): Privilege escalation in n/a (critical 10.0)
- [CVE-2012-5196](https://insights.sbomify.com/CVE-2012-5196/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-5197](https://insights.sbomify.com/CVE-2012-5197/): Other in n/a (critical 10.0)
- [CVE-2012-3416](https://insights.sbomify.com/CVE-2012-3416/): Auth bypass in n/a (critical 10.0)
- [CVE-2008-3424](https://insights.sbomify.com/CVE-2008-3424/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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