dbcve.org
CondorApplication · Condor Project

CVE-2012-3416

HIGH · 10.0 CVSS v2.0 Published 2012-08-25
Fix available
A fix is available. Upgrade to after 7.8.1 or later.
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
Condor before 7.8.2 allows remote attackers to bypass host-based authentication and execute actions such as ALLOW_ADMINISTRATOR or ALLOW_WRITE by connecting from a system with a spoofed reverse DNS hostname.

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 · high confidence

Condor before version 7.8.2 contains a security flaw where host-based authentication can be bypassed by attackers connecting from systems with spoofed reverse DNS hostnames. This allows remote unauthenticated attackers to execute privileged operations such as ALLOW_ADMINISTRATOR or ALLOW_WRITE by manipulating DNS resolution.

MitigationUpgrade Condor to version 7.8.2 or later where this vulnerability is patched. Consider implementing additional authentication mechanisms (such as GSI, Kerberos, or certificate-based authentication) to supplement host-based checks.

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.8.1= 6.5.4= 6.8.0= 6.8.1= 6.8.2= 6.8.3= 6.8.4= 6.8.5= 6.8.6= 6.8.7= 6.8.8= 6.8.9

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 Condor version
    Run `condor_version` or `condor_q -version` to retrieve the installed Condor version number
    Affected if The version is 7.8.1 or earlier, or one of these: 6.5.4, 6.8.0, 6.8.1, 6.8.2, 6.8.3, 6.8.4, 6.8.5, 6.8.6, 6.8.7, 6.8.8, or 6.8.9
  2. Locate Condor configuration files
    Check for the main configuration file (typically /etc/condor/condor_config or $CONDOR_CONFIG) and any local configuration in /etc/condor/config.d/
    Affected if Configuration files exist and host-based authentication is configured
  3. Inspect host-based access control settings
    Search the Condor configuration for ALLOW_ADMINISTRATOR, ALLOW_WRITE, ALLOW_READ, or similar directives that use hostnames or IP addresses (for example: ALLOW_WRITE = *.example.com or ALLOW_ADMINISTRATOR = *.localdomain)
    Affected if Any ALLOW_ADMINISTRATOR or ALLOW_WRITE directive uses host-based (DNS/IP) matching rather than stronger authentication methods
  4. Verify DNS resolution configuration
    Examine the Condor configuration for DNS_DOMAIN_NAME setting and review whether reverse DNS lookups are used for authentication
    Affected if The Condor pool relies on DNS-based host verification without additional authentication layers

You are affected if your Condor version is 7.8.1 or earlier (or version 6.5.4 through 6.8.9) AND your configuration uses host-based authentication rules like ALLOW_WRITE or ALLOW_ADMINISTRATOR that rely on DNS hostname resolution.

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
Upgrade available Upgrade to a release after 7.8.1
Interim mitigation

Upgrade Condor to version 7.8.2 or later where this vulnerability is patched. Consider implementing additional authentication mechanisms (such as GSI, Kerberos, or certificate-based authentication) to supplement host-based checks.

Recommended fix High confidence

Condor 7.8.2 or later

  1. 1. Back up your current Condor configuration files (typically in /etc/condor/ or /usr/local/etc/)
  2. 2. Download Condor version 7.8.2 or later from the official Condor release repository (https://research.cs.wisc.edu/condor/)
  3. 3. Stop the Condor service: 'condor_off -master' or 'systemctl stop condor'
  4. 4. Install the new Condor package using your system's package manager (rpm, dpkg, or yum/apt)
  5. 5. Restore your backed-up configuration files to the appropriate directory
  6. 6. Start the Condor service: 'condor_on' or 'systemctl start condor'
  7. 7. Verify the Condor version is 7.8.2 or later using 'condor_version'
  8. 8. Test that host-based authentication is functioning correctly with the fix
Caveat Review release notes for 7.8.2 for any configuration or behavior changes from your current version; test in staging before production deployment

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

Fix this in Condor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-3416 — 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-3416 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