dbcve.org
HtcondorApplication · Wisc

CVE-2021-45101

HIGH · 8.1 CVSS v3.1 Published 2021-12-16
Fix available
A fix is available. Upgrade to after 9.0.2 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
An issue was discovered in HTCondor before 8.8.15, 9.0.x before 9.0.4, and 9.1.x before 9.1.2. Using standard command-line tools, a user with only READ access to an HTCondor SchedD or Collector daemon can discover secrets that could allow them to control other users' jobs and/or read their data.

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

A user with only READ access to HTCondor SchedD (Scheduler Daemon) or Collector daemon can discover sensitive secrets (credentials/tokens) that should be protected, allowing unauthorized control of other users' jobs or access to their data. This is an information disclosure vulnerability in the access control logic.

MitigationUpgrade HTCondor to version 8.8.15, 9.0.4, or 9.1.2 or later. Additionally, review and rotate any credentials that may have been exposed, and audit access control configurations.

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
HtcondorApplication
Affected:<= 8.8.13>= 9.0.0, <= 9.0.2= 9.1.0

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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. Identify HTCondor version
    Run 'condor_version' command or check the installed package version using your system package manager (e.g., 'rpm -q htcondor' or 'dpkg -l htcondor')
    Affected if The installed version is <= 8.8.13, OR >= 9.0.0 and <= 9.0.2, OR exactly 9.1.0
  2. Determine if SchedD daemon is running
    Run 'condor_status -schedd' or check for the 'condor_schedd' process using 'ps aux | grep schedd'
    Affected if The SchedD daemon is running and accessible to the user in question
  3. Determine if Collector daemon is running
    Run 'condor_status' or check for the 'condor_collector' process using 'ps aux | grep collector'
    Affected if The Collector daemon is running and accessible to the user in question
  4. Verify READ access is enabled for the daemons
    Examine HTCondor configuration files (default locations: /etc/condor/condor_config or /etc/condor/config.d/) for ALLOW_READ settings. Use 'condor_config_val -all' to view effective configuration. Look for settings like ALLOW_READ, ALLOW_CLIENT, or authorization rules that grant read access.
    Affected if Users with only READ-level access can query the SchedD or Collector daemon (the vulnerability requires read access to be granted to non-privileged users)

You are affected if your installed HTCondor version falls within the vulnerable ranges AND either the SchedD or Collector daemon is running with READ access granted to the user in question.

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 9.0.2
Interim mitigation

Upgrade HTCondor to version 8.8.15, 9.0.4, or 9.1.2 or later. Additionally, review and rotate any credentials that may have been exposed, and audit access control configurations.

Recommended fix High confidence

Upgrade to HTCondor 8.8.15+ (8.x branch), 9.0.4+ (9.0.x branch), or 9.1.2+ (9.1.x branch)

  1. Identify your current HTCondor version using `condor_version` or checking your package manager
  2. Stop the HTCondor services: `condor_stop` or your system's service management tool
  3. Upgrade HTCondor to version 8.8.15 or later for the 8.x branch, OR version 9.0.4 or later for the 9.0.x branch, OR version 9.1.2 or later for the 9.1.x branch
  4. Verify the upgrade was successful by running `condor_version`
  5. Restart HTCondor services: `condor_start` or your system's service management tool
  6. Verify the security fix is in place by testing that READ-only users can no longer access sensitive job secrets
Caveat Review HTCondor release notes for any configuration or feature changes between your current version and the target upgrade version before deploying

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

Fix this in Htcondor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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