Apache POI in versions prior to release 3.17 are vulnerable to Denial of Service Attacks: 1) Infinite Loops while parsing crafted WMF, EMF, MSG and macros (POI bugs 61338 and 61294), and 2) Out of Memory Exceptions while parsing crafted DOC, PPT and XLS (POI bugs 52372 and 61295).
Apache POI - Java API To Access Microsoft Format Files
Path to dependency file: /pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/poi/poi/3.10-FINAL/poi-3.10-FINAL.jar
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2017-12626
### Vulnerable Library - poi-3.10-FINAL.jarApache POI - Java API To Access Microsoft Format Files
Path to dependency file: /pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/poi/poi/3.10-FINAL/poi-3.10-FINAL.jar
Dependency Hierarchy: - :x: **poi-3.10-FINAL.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.joychou.controller.othervulns.ooxmlXXE (Application) -> org.apache.poi.xssf.usermodel.XSSFWorkbook (Extension) -> org.apache.poi.xssf.usermodel.XSSFCreationHelper (Extension) -> org.apache.poi.xssf.usermodel.XSSFFormulaEvaluator (Extension) ... -> org.apache.poi.hssf.usermodel.HSSFWorkbook (Extension) -> org.apache.poi.hpsf.PropertySet (Extension) -> ❌ org.apache.poi.hpsf.Section (Vulnerable Component) ``` ### Vulnerability DetailsApache POI in versions prior to release 3.17 are vulnerable to Denial of Service Attacks: 1) Infinite Loops while parsing crafted WMF, EMF, MSG and macros (POI bugs 61338 and 61294), and 2) Out of Memory Exceptions while parsing crafted DOC, PPT and XLS (POI bugs 52372 and 61295).
Publish Date: 2018-01-29
URL: CVE-2017-12626
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 1.4000001%
### CVSS 3 Score Details (7.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://lists.apache.org/thread.html/453d9af5dbabaccd9afb58d27279a9dbfe8e35f4e5ea1645ddd6960b@%3Cdev.poi.apache.org%3E
Release Date: 2018-01-26
Fix Resolution: 3.17-beta1
In order to enable automatic remediation, please create workflow rules
WS-2016-7061
### Vulnerable Library - poi-3.10-FINAL.jarApache POI - Java API To Access Microsoft Format Files
Path to dependency file: /pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/poi/poi/3.10-FINAL/poi-3.10-FINAL.jar
Dependency Hierarchy: - :x: **poi-3.10-FINAL.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.joychou.controller.othervulns.ooxmlXXE (Application) -> org.apache.poi.xssf.usermodel.XSSFSheet (Extension) -> org.apache.poi.hssf.record.PasswordRecord (Extension) -> org.apache.poi.hssf.record.Record (Extension) ... -> org.apache.poi.hssf.record.CFRuleRecord (Extension) -> org.apache.poi.hssf.usermodel.HSSFWorkbook (Extension) -> ❌ org.apache.poi.poifs.filesystem.Ole10Native (Vulnerable Component) ``` ### Vulnerability DetailsApache POI before 3.16-beta1 is vulnerable to bufferoverflow attack due to lack of length sanity check for length of embedded OLE10Native.
Publish Date: 2016-10-14
URL: WS-2016-7061
### Threat AssessmentExploit Maturity: Not Defined
EPSS:
### CVSS 3 Score Details (4.8)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Release Date: 2016-10-14
Fix Resolution: 3.16-beta1
In order to enable automatic remediation, please create workflow rules
In order to enable automatic remediation for this issue, please create workflow rules