Application exception via unchecked array index
Published Nov 26, 2023 · Updated Feb 13, 2025
Improper array-index validation in Apryse iText 8.0.2 allows remote attackers to trigger an exception through crafted input. The report attributes the failure to main in PdfDocument.java but does not identify the array access or the attacker-controlled value used as its index. A consuming application must process the input; Apryse confirms managed bounds exceptions in Java and C# but disputes that the behavior has a security consequence.
Summary
What happened
Improper array-index validation in Apryse iText 8.0.2 allows remote attackers to trigger an exception through crafted input. The report attributes the failure to main in PdfDocument.java but does not identify the array access or the attacker-controlled value used as its index. A consuming application must process the input; Apryse confirms managed bounds exceptions in Java and C# but disputes that the behavior has a security consequence.
The record
- CVE
- CVE-2023-6298
- Published
- Nov 26, 2023
- Updated
- Feb 13, 2025
- Vendor
- Apryse
- Product
- iText
- Classifications
- CWE-129
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 26, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Exception-triggering proof-of-concept samplesproof of concept · demonstrated
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