dbcve.org
CondorApplication · Condor Project

CVE-2012-5196

HIGH · 10.0 CVSS v2.0 Published 2012-09-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple buffer overflows in Condor 7.6.x before 7.6.10 and 7.8.x before 7.8.4 have unknown impact and attack vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Multiple buffer overflow vulnerabilities exist in HTCondor (a distributed high-throughput computing workload management system) affecting versions 7.6.x before 7.6.10 and 7.8.x before 7.8.4. The CVSS score of 10 indicates critical severity, typically associated with remote unauthenticated code execution, though specific technical details of the overflows and attack vectors are not provided.

MitigationUpgrade HTCondor installations to version 7.6.10, 7.8.4, or later to remediate the buffer overflow vulnerabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CondorApplication
Affected:= 7.6.0= 7.6.1= 7.6.2= 7.6.3= 7.6.4= 7.6.5= 7.6.6= 7.6.7= 7.6.8= 7.6.9= 7.8.0= 7.8.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check HTCondor version with condor_version
    Run the command 'condor_version' on the host
    Affected if The output shows version 7.6.0 through 7.6.9 or 7.8.0 through 7.8.3
  2. Verify version with condor_q
    Run 'condor_q -version' to get version information
    Affected if The displayed version falls within 7.6.0-7.6.9 or 7.8.0-7.8.3
  3. Check package version via RPM
    If installed via RPM, run 'rpm -q condor' or 'rpm -qa | grep condor'
    Affected if The package version shown is one of the affected versions (7.6.x where x is 0-9, or 7.8.x where x is 0-3)
  4. Check package version via DEB
    If installed via DEB, run 'dpkg -l | grep condor' or 'dpkg-query -W condor'
    Affected if The displayed package version is in the affected range 7.6.0-7.6.9 or 7.8.0-7.8.3

The system is affected if HTCondor is installed and its version is 7.6.0 through 7.6.9 or 7.8.0 through 7.8.3.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HTCondor installations to version 7.6.10, 7.8.4, or later to remediate the buffer overflow vulnerabilities.

Recommended fix High confidence

Condor 7.6.10 or later (or 7.8.4+ for the 7.8.x branch)

  1. 1. Identify the current Condor installation version using: condor_version or condor_q -version
  2. 2. Confirm the installed version is one of the affected releases: 7.6.0, 7.6.1, 7.6.2, or 7.6.3
  3. 3. Backup current Condor configuration files (typically in /etc/condor/ or /opt/condor/)
  4. 4. Stop the Condor daemon: condor_master -shutdown or systemctl stop condor
  5. 5. Download the updated Condor release from the official HTCondor distribution (https://research.cs.wisc.edu/htcondor/)
  6. 6. Install Condor version 7.6.10 or later (or 7.8.4+ for the 7.8.x branch)
  7. 7. Verify the installation: condor_version
  8. 8. Restart Condor services: condor_start or systemctl start condor
Caveat Review release notes for configuration changes between 7.6.x and 7.6.10; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Condor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-5196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-5196 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data