CVE-2017-16816
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 condor_schedd component in HTCondor before 8.6.8 and 8.7.x before 8.7.5 allows remote authenticated users to cause a denial of service (daemon crash) by leveraging use of GSI and VOMS extensions.
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 confidenceThe condor_schedd component in HTCondor versions prior to 8.6.8 and 8.7.5 contains a vulnerability allowing remote authenticated users to crash the daemon (denial of service) by exploiting the GSI (Grid Security Infrastructure) and VOMS (Virtual Organization Membership Service) extensions.
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< 8.6.8>= 8.7.0, < 8.7.5CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify HTCondor versionRun `condor_version` or check the installed package version using your system's package manager (e.g., `rpm -q htcondor` or `dpkg -l htcondor`)Affected if version is less than 8.6.8, or greater than or equal to 8.7.0 but less than 8.7.5
-
Confirm condor_schedd component is in useRun `condor_status -schedd` to list active schedd daemons, or check for condor_schedd process running via `ps aux | grep condor_schedd`Affected if condor_schedd is running or configured on the system
-
Determine if GSI or VOMS authentication is enabledExamine the HTCondor configuration files (typically in /etc/condor/ or locations pointed to by $CONDOR_CONFIG) for SEC_ENABLE_GSI or SEC_ENABLE_VOMS settings, or check for grid mapfile configurationsAffected if GSI or VOMS authentication is explicitly enabled in the security configuration
-
Verify the security configuration exposes the schedd to remote authenticated usersReview the condor_schedd configuration for ALLOW_* or DENY_* settings that permit remote authenticated connections, particularly in the context of GSI/VOMS credentialsAffected if remote authenticated access via GSI/VOMS is permitted to the schedd
System is affected if running a vulnerable HTCondor version (below 8.6.8 or 8.7.0-8.7.4) with condor_schedd active and GSI/VOMS authentication enabled for remote users
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 data8.6.88.7.5
Upgrade HTCondor to version 8.6.8, 8.7.5, or later to patch the vulnerability in the condor_schedd component.
- Consultation2.0 h
- Implementation3.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 $3,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16816 — 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-2017-16816 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