CVE-2012-5390
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 · uneditedThe standard universe shadow (condor_shadow.std) component in Condor 7.7.3 through 7.7.6, 7.8.0 before 7.8.5, and 7.9.0 does no properly check privileges, which allows remote attackers to gain privileges via a crafted standard universe job.
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 confidenceThe condor_shadow.std component in HTCondor (Condor) versions 7.7.3 through 7.7.6, 7.8.0 before 7.8.5, and 7.9.0 fails to properly validate privileges when handling standard universe jobs, allowing remote attackers to submit crafted jobs that execute with elevated privileges on the submit machine.
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= 7.9.0= 7.8.0= 7.8.1= 7.8.2= 7.8.3= 7.8.4= 7.7.3= 7.7.4= 7.7.5= 7.7.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if HTCondor is installedRun 'condor_version' or 'condor_q -version' to get the installed HTCondor versionAffected if The version output matches 7.7.3, 7.7.4, 7.7.5, 7.7.6, 7.8.0, 7.8.1, 7.8.2, 7.8.3, 7.8.4, or 7.9.0
-
Verify the condor_shadow.std binary existsLocate the condor_shadow.std binary on the submit machine using 'find / -name condor_shadow.std 2>/dev/null' or check the Condor sbin directoryAffected if The condor_shadow.std binary is present on the system
-
Confirm standard universe is enabledCheck the Condor configuration file (condor_config) for ENABLE_STANDARD_UNIVERSE = TRUE or check if any jobs are submitted with the 'standard' universe by running 'condor_q -pool localhost -run' and inspecting job attributesAffected if Standard universe execution mode is enabled or jobs using the standard universe are present in the queue
You are affected if HTCondor version 7.7.3-7.7.6, 7.8.0-7.8.4, or 7.9.0 is installed AND the standard universe feature is enabled with the condor_shadow.std component present.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to Condor 7.8.5+, 7.9.1+, or the latest stable version. If immediate patching is not feasible, disable the standard universe execution mode or restrict submission access through ACLs and network segmentation.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-5390 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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