LiveActive security incident?Get immediate response
CVE Record

CVE-2022-32208: When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly.

When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-32208 affects curl before 7.84.0 when using Kerberos 5-secured FTP. A network attacker positioned in the traffic path could make message verification failures go unnoticed and inject data to the client. Exposure is narrow, but curl is widely embedded, so inventory matters.

Executive priority

Treat this as a targeted remediation item, not an emergency. Prioritize environments using Kerberos-secured FTP or sensitive internal file transfers, then close remaining exposure through normal curl and OS patch cycles.

Technical view

The flaw is in curl FTP transfers protected by krb5. Verification failure handling is incorrect, enabling a man-in-the-middle condition to evade detection and inject client-bound data. The CVSS 3.1 score is 5.9 with network attack vector, high attack complexity, no privileges, and no user interaction.

Likely exposure

Most risk is in systems running curl or libcurl before 7.84.0 that actually perform FTP transfers secured by Kerberos 5. General curl installations without krb5 FTP usage are less likely exposed. Vendor-packaged curl should be checked against OS and appliance advisories.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Practical abuse requires a man-in-the-middle position and the specific krb5-secured FTP path, which limits likelihood but can matter on sensitive internal networks.

Researcher notes

Evidence is strongest for curl before 7.84.0 and vendor-package remediation. The bundle does not provide exploit code, confirmed exploitation, or detailed affected-version ranges beyond the upstream fixed version. Validate exposure by feature use, not curl presence alone.

Mitigation direction

  • Upgrade curl or libcurl to 7.84.0 or later.
  • Apply fixed packages from Debian, Fedora, Gentoo, Apple, NetApp, or relevant vendors.
  • Inventory applications and appliances bundling libcurl.
  • Identify and reduce krb5-secured FTP usage where updates are delayed.
  • Check vendor guidance for unsupported or embedded curl copies.

Validation and detection

  • Confirm installed curl and libcurl versions across servers, images, and appliances.
  • Check whether any workloads use FTP with Kerberos 5 protection.
  • Map vendor advisories to deployed operating systems and products.
  • Verify package updates include the CVE-2022-32208 fix.
  • Prioritize systems on networks where interception is plausible.
Prepared
Confidence
high
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-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-2022-32208 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
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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
8Source 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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2022-32208Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ahttps://github.com/curl/curlFixed in 7.84.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.