Gvfs: sftp: heap-based buffer overflow in read_reply()
- 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 1.60.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: no
- Technical impact: total
Summary
A flaw was found in the SFTP backend in gvfs. When mounting a share and reading a file, a malicious SFTP server can cause read_reply() to process a length that exceeds the size requested by the client. The function does not verify the server-provided length against the allocated buffer size, causing the operation to write past the intended boundaries. This issue allows a malicious server to corrupt adjacent heap memory in the gvfsd-sftp process, resulting in a denial of service as the process aborts upon detecting the heap corruption or potentially allowing arbitrary code execution.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- gvfs
fixed in 1.60.2
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported
- gvfs
Version range not reported