Rendered-content integrity loss via improper Textile sanitization
Published Apr 6, 2021 · Updated Aug 5, 2024
Improper markup sanitization in Redmine before 3.4.13 and 4.x before 4.0.6 allows remote attackers to alter rendered Textile output. The Textile formatter mishandles markup data during sanitization, but Redmine has not published the malformed construct or exact filtering operation. Network access to submit content rendered as Textile is required; published scoring limits the consequence to rendered-output integrity, with no confidentiality or availability impact.
Summary
What happened
Improper markup sanitization in Redmine before 3.4.13 and 4.x before 4.0.6 allows remote attackers to alter rendered Textile output. The Textile formatter mishandles markup data during sanitization, but Redmine has not published the malformed construct or exact filtering operation. Network access to submit content rendered as Textile is required; published scoring limits the consequence to rendered-output integrity, with no confidentiality or availability impact.
The record
- CVE
- CVE-2019-25026
- Published
- Apr 6, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
No sourced classifications are available.
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