dbcve.org
HtcondorApplication · Wisc

CVE-2021-45103

HIGH · 8.1 CVSS v3.1 Published 2022-04-06
Fix available
A fix is available. Upgrade to 9.0.10 / 9.6.0 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 9.0.x before 9.0.10 and 9.1.x before 9.5.1. An attacker can access files stored in S3 cloud storage that a user has asked HTCondor to transfer.

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

HTCondor versions 9.0.x before 9.0.10 and 9.1.x before 9.5.1 contain a broken access control vulnerability in S3 cloud storage transfer functionality. An attacker can access files stored in S3 that a user has asked HTCondor to transfer, indicating improper authorization checks allowing unauthorized access to sensitive cloud-stored data.

MitigationUpgrade HTCondor to version 9.0.10, 9.5.1, or later to remediate the vulnerability. Verify S3 access controls and audit any suspicious file transfer activity that occurred prior to patching.

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.9.4, < 9.0.10>= 9.1.0, < 9.6.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. Check installed HTCondor version
    Run 'condor_version' command or 'rpm -q htcondor' to determine the installed version number
    Affected if Version is 9.0.x before 9.0.10, or 9.1.x before 9.5.1, or between 9.5.1 and 9.6.0 (9.0.0-9.0.9.x, 9.1.0-9.5.0.x, 9.6.0 is also listed as affected in the range)
  2. Verify S3 cloud transfer is in use
    Search HTCondor configuration files (condor_config, local config) for S3-related parameters such as CLOUD_STAR or any S3_ENDPOINT settings, or check job submit files for transfer_input_files or transfer_output_files using S3 URLs
    Affected if S3 transfer functionality is configured and actively used for file transfers
  3. Inspect S3 access controls
    Review the S3 bucket policies and IAM policies associated with the credentials HTCondor is using to verify which principals have access to transferred files
    Affected if The S3 credentials or bucket allow broader access than intended, or if HTCondor can access files from other users' S3 paths

You are affected if your HTCondor version falls within the vulnerable range AND S3 cloud storage transfer is enabled in your configuration.

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 9.0.10 / 9.6.0 or later
Fixed in 9.0.109.6.0
Interim mitigation

Upgrade HTCondor to version 9.0.10, 9.5.1, or later to remediate the vulnerability. Verify S3 access controls and audit any suspicious file transfer activity that occurred prior to patching.

Recommended fix High confidence

Upgrade to HTCondor 9.0.10 (for 9.0.x branch) or 9.6.0+ (for 9.1.x+ branch); prefer 9.6.0 or later for comprehensive coverage

  1. 1. Identify the currently installed HTCondor version using 'condor_version' or checking your package manager.
  2. 2. For HTCondor 9.0.x users (versions 9.0.0 through 9.0.9): Upgrade to version 9.0.10 or later.
  3. 3. For HTCondor 9.1.x through 9.5.x users: Upgrade to version 9.6.0 or later (the latest stable 9.x release).
  4. 4. For HTCondor 8.9.4+ users: Upgrade to at least 9.0.10, or better to 9.6.0+ for the most complete fix.
  5. 5. After upgrade, verify the version with 'condor_version' to confirm the patch was applied.
Caveat Upgrading across major 8.x to 9.x branches may introduce configuration changes; review HTCondor release notes for breaking changes between 8.x and 9.x

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

Fix this in Htcondor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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