LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22923: When curl is instructed to get content using the metalink feature, and a user name and password are used to...

When curl is instructed to get content using the metalink feature, and a user name and password are used to download the metalink XML file, those same credentials are then subsequently passed on to each of the servers from which curl will download or try to download the contents from. Often contrary to the user's expectations and intentions and without telling the user it happened.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This curl issue can unintentionally expose credentials. If curl downloads a metalink XML file using a username and password, it may reuse those credentials when contacting every listed content server. That can disclose secrets to servers the user did not intend to authenticate to.

Executive priority

Treat this as a targeted credential-exposure cleanup rather than an emergency remote-code-execution event. Prioritize environments where curl download automation handles secrets or uses third-party mirrors, because credential leakage can create downstream account or supply-chain risk.

Technical view

CVE-2021-22923 affects curl 7.27.0 through 7.77.0. With the metalink feature, credentials used to fetch the metalink XML are subsequently passed to each server curl tries for the referenced content, contrary to likely user expectations.

Likely exposure

Exposure is most likely in automation, build systems, download tooling, or packaged products that use curl metalink downloads with username/password authentication. Systems that do not use metalink or do not authenticate the metalink XML request are less likely exposed.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The risk is credential disclosure through normal curl behavior when a user or script combines metalink downloads with credentials, especially where listed mirrors are not equally trusted.

Researcher notes

Evidence is specific to curl metalink credential propagation. The bundle lacks CVSS scoring, exploit telemetry, and detailed fixed-version text, so validation should focus on affected version inventory, metalink workflow review, and vendor advisory confirmation rather than assumptions about broader curl usage.

Mitigation direction

  • Upgrade curl beyond affected versions using vendor-supported packages.
  • Review Fedora, Gentoo, Oracle, NetApp, Siemens, or relevant vendor advisories.
  • Avoid using metalink downloads with credentials unless vendor guidance confirms safety.
  • Remove embedded credentials from curl automation where possible.
  • Rotate credentials if logs or mirrors may have received unintended authentication data.

Validation and detection

  • Inventory curl versions and flag 7.27.0 through 7.77.0.
  • Search automation for curl metalink usage with username or password options.
  • Review product advisories for embedded or bundled curl exposure.
  • Check whether download mirrors received unintended authenticated requests.
  • Confirm patched curl versions after remediation.
Prepared
Confidence
medium
Sources
8

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-319: 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
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-22923 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

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-319 · source CWE mapping

Cleartext Transmission of Sensitive Information

Cleartext Transmission of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.