SmartBear / ready-jira-plugin

Provides ReadyAPI - Jira integration based on Jira rest API
4 stars 7 forks source link

CVE-2019-10086 (High) detected in commons-beanutils-1.9.3.jar - autoclosed #80

Closed mend-for-github-com[bot] closed 3 years ago

mend-for-github-com[bot] commented 3 years ago

CVE-2019-10086 - High Severity Vulnerability

Vulnerable Library - commons-beanutils-1.9.3.jar

Apache Commons BeanUtils provides an easy-to-use but flexible wrapper around reflection and introspection.

Library home page: https://commons.apache.org/proper/commons-beanutils/

Path to dependency file: ready-jira-plugin/pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar

Dependency Hierarchy: - ready-api-soapui-ng-3.5.0.jar (Root Library) - ready-api-security-3.5.0.jar - ready-api-core-3.5.0.jar - :x: **commons-beanutils-1.9.3.jar** (Vulnerable Library)

Found in HEAD commit: 93947352bde9f88c621863f93d8141d10d07612e

Found in base branch: master

Vulnerability Details

In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects. We, however were not using this by default characteristic of the PropertyUtilsBean.

Publish Date: 2019-08-20

URL: CVE-2019-10086

CVSS 3 Score Details (7.3)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/victims/victims-cve-db/commit/16a669c84d95bbbd4294f30e609049a36700847f

Release Date: 2019-08-20

Fix Resolution: commons-beanutils:commons-beanutils:1.9.4

mend-for-github-com[bot] commented 3 years ago

:heavy_check_mark: This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.