FedoraOperating system · Fedoraproject
CVE-2020-24614
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 · uneditedFossil before 2.10.2, 2.11.x before 2.11.2, and 2.12.x before 2.12.1 allows remote authenticated users to execute arbitrary code. An attacker must have check-in privileges on the repository.
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 confidenceFossil SCM versions before 2.10.2, 2.11.x before 2.11.2, and 2.12.x before 2.12.1 contain a vulnerability allowing remote authenticated users with check-in privileges to execute arbitrary code, likely through improper validation or sanitization of check-in operations.
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
FedoraOperating system
= 32= 33< 2.10.2>= 2.11.0, < 2.11.2>= 2.12.0, < 2.12.1= 15.0= 15.1= 15.2CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Check Fossil SCM versionRun `fossil --version` or `fossil version` to obtain the installed version numberAffected if The version is less than 2.10.2, or falls between 2.11.0 and 2.11.2 (inclusive), or falls between 2.12.0 and 2.12.1 (inclusive)
-
Verify Fossil server version if serving repositoriesIf Fossil is running as a server (fossil server or fossil http), check the version of the fossil binary serving the repositoryAffected if The server's Fossil version is within the vulnerable ranges listed above
-
Check package version on FedoraRun `rpm -q fossil` to query the installed Fossil package versionAffected if The RPM version is lower than 2.10.2-1 or falls within the affected version ranges
-
Check package version on openSUSERun `rpm -q fossil` or check via zypper to determine the installed versionAffected if The package version is lower than the fixed versions for openSUSE Leap 15.1/15.2 or Backports SLE 15.0
You are affected if your Fossil SCM installation version is less than 2.10.2, or is any version between 2.11.0 and 2.11.2, or is any version between 2.12.0 and 2.12.1, and you allow authenticated users to perform check-in operations.
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 data2.10.22.11.22.12.1
Upgrade Fossil to version 2.10.2, 2.11.2, 2.12.1 or later. As a compensating control, restrict check-in privileges to only trusted users and audit existing user permissions.
Fix this in Fedora
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24614 — 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-2020-24614 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