Content injection via unescaped login-page path
Published Jun 24, 2020 · Updated Aug 4, 2024
Content injection in GNU Mailman before 2.1.33 allows remote attackers to alter a private archive login page through a crafted URL. Cgi/private.py fails to neutralize attacker-controlled path content before rendering it in the login page. Exploitation requires the list's private_roster setting to be Anyone and a victim to open the crafted page; the documented effect is page-content modification.
Summary
What happened
Content injection in GNU Mailman before 2.1.33 allows remote attackers to alter a private archive login page through a crafted URL. Cgi/private.py fails to neutralize attacker-controlled path content before rendering it in the login page. Exploitation requires the list's private_roster setting to be Anyone and a victim to open the crafted page; the documented effect is page-content modification.
The record
- CVE
- CVE-2020-15011
- Published
- Jun 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-74, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 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.
Weakness, pattern, technique
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