When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches. curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using and trustingthe responses it got *before* the TLS handshake as if they were authenticated.Using this flaw, it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS traffic from the legitimate server and trick curl into sending data back to the user thinking the attacker's injected data comes from the TLS-protected server.
https://www.oracle.com/security-alerts/cpuoct2021.html
https://www.oracle.com/security-alerts/cpujul2022.html
https://www.oracle.com/security-alerts/cpujan2022.html
https://www.oracle.com/security-alerts/cpuapr2022.html
https://www.debian.org/security/2022/dsa-5197
https://support.apple.com/kb/HT213183
https://security.netapp.com/advisory/ntap-20211029-0003/
https://security.gentoo.org/glsa/202212-01
https://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
https://lists.debian.org/debian-lts-announce/2021/09/msg00022.html
https://hackerone.com/reports/1334763
https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf