VYPR
Unrated severityNVD Advisory· Published Jul 7, 2022· Updated May 5, 2025

CVE-2022-32208

CVE-2022-32208

Description

A flaw in curl's handling of krb5-secured FTP transfers allows MITM attacks to go undetected and inject data into the client.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A flaw in curl's handling of krb5-secured FTP transfers allows MITM attacks to go undetected and inject data into the client.

Vulnerability

In curl versions prior to 7.84.0, when performing FTP transfers secured by Kerberos (krb5), the library incorrectly handles message verification failures. This allows a Man-In-The-Middle attacker to inject data into the client without detection. The affected versions are all curl releases before 7.84.0.

Exploitation

An attacker with network position to intercept FTP traffic can exploit this by sending crafted responses that fail krb5 verification. Due to the flawed handling, the client does not detect the verification failure, allowing the attacker to inject arbitrary data into the FTP data stream.

Impact

Successful exploitation enables a Man-In-The-Middle attacker to inject data into the client's FTP transfer, potentially leading to data corruption or injection of malicious content. The integrity of the FTP session is compromised, and the attack goes unnoticed by the client.

Mitigation

The vulnerability is fixed in curl version 7.84.0 and later. Users should upgrade to at least curl 7.84.0. For systems where upgrade is not immediately possible, consider disabling krb5-secured FTP transfers or using alternative secure transfer methods. The Gentoo security advisory [3] recommends upgrading to curl 7.86.0 or later.

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

43

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

9

News mentions

0

No linked articles in our index yet.