Libsoup: null pointer dereference in soup_message_headers_get_content_disposition when "filename" parameter is present, but has no value in content-disposition header
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.6.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
A flaw was found in libsoup, where the soup_message_headers_get_content_disposition() function is vulnerable to a NULL pointer dereference. This flaw allows a malicious HTTP peer to crash a libsoup client or server that uses this function.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- libsoup
fixed in 3.6.2
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- mingw-freetype
Version range not reported
- spice-client-win
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup
Version range not reported
- libsoup3
Version range not reported
- libsoup
Version range not reported