Unauthenticated code execution via awarrensmtp heap overflow
Published Jun 18, 2020 · Updated Aug 4, 2024
Heap-based buffer overflow in Sophos XG Firewall 17.5 MR11 and earlier allows remote attackers to execute arbitrary code. The awarrensmtp firmware component overflows a heap buffer, but Sophos has not disclosed the triggering input or faulty copy operation. No authentication or user interaction is required, and successful exploitation grants code execution on the firewall.
Summary
What happened
Heap-based buffer overflow in Sophos XG Firewall 17.5 MR11 and earlier allows remote attackers to execute arbitrary code. The awarrensmtp firmware component overflows a heap buffer, but Sophos has not disclosed the triggering input or faulty copy operation. No authentication or user interaction is required, and successful exploitation grants code execution on the firewall.
The record
- CVE
- CVE-2020-11503
- Published
- Jun 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 18, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo