LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22922: When curl is instructed to download content using the metalink feature, thecontents is verified against a h...

When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same contentfrom a set of different URLs, potentially hosted by different servers and theclient can then download the file from one or several of them. In a serial orparallel manner.If one of the servers hosting the contents has been breached and the contentsof the specific file on that server is replaced with a modified payload, curlshould detect this when the hash of the file mismatches after a completeddownload. It should remove the contents and instead try getting the contentsfrom another URL. This is not done, and instead such a hash mismatch is onlymentioned in text and the potentially malicious content is kept in the file ondisk.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects curl downloads that use metalink files. If one mirror serves tampered content, curl can detect the hash mismatch but still leave the bad file on disk. The main business risk is file integrity in software retrieval or automation workflows that relied on curl metalink verification.

Executive priority

Treat as moderate priority unless metalink downloads support software distribution, build pipelines, or operational automation. In those environments, prioritize remediation because the flaw undermines a control meant to prevent tampered files from being retained.

Technical view

CVE-2021-22922 affects curl 7.27.0 through 7.77.0. In metalink downloads, curl verifies content against the metalink XML hash, but on mismatch it only reports the problem and keeps the potentially malicious file instead of deleting it and trying another URL. CVSS 3.1 is 6.5 with high integrity impact.

Likely exposure

Exposure is most likely where affected curl versions are used with the metalink feature, especially package retrieval, installers, images, or automation that accepts downloaded files after curl exits. Systems with curl present but no metalink usage have lower practical exposure based on the provided evidence.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not marked KEV. Exploitation would require a user or automation path using metalink downloads and a compromised or malicious content source among the listed mirrors. No public weaponization evidence is provided here.

Researcher notes

The key condition is metalink-specific behavior after a hash mismatch, not general curl downloading. Evidence supports high integrity impact but no confidentiality or availability impact. Downstream advisories from Fedora, Gentoo, Oracle, NetApp, Siemens, and Apache Kafka image discussions indicate ecosystem relevance.

Mitigation direction

  • Upgrade curl using vendor-supported packages outside the affected version range.
  • Review vendor advisories for downstream products bundling curl.
  • Avoid metalink-based download workflows until affected curl versions are removed.
  • Ensure automation rejects downloads when curl reports hash mismatch.
  • Re-fetch critical artifacts from trusted sources after remediation.

Validation and detection

  • Inventory curl versions and identify 7.27.0 through 7.77.0.
  • Search build, installer, and operations scripts for metalink usage.
  • Check downstream vendor advisories for embedded curl exposure.
  • Confirm patched systems no longer run affected curl builds.
  • Review logs or job output for historical hash mismatch warnings.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-840: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-22922 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-22922Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ahttps://github.com/curl/curlcurl 7.27.0 to and including 7.77.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-840 · source CWE mapping

Business Logic Errors

Business Logic Errors represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.