How severe is CVE-2017-10031?

CVE-2017-10031 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.

Is CVE-2017-10031 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-10031?

CVE-2017-10031 primarily affects Oracle Communications Convergence. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-10031?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-10031 published?

CVE-2017-10031 was published on 2017-08-08 and last updated on 2026-06-17.

CVE-2017-10031

CVE-2017-10031 is a high-severity vulnerability in Oracle Communications Convergence with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.2)
CVSS v2: 6.4
EPSS exploit prediction: 2% (73rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Communications Convergence
Published: 2017-08-08
Last modified: 2026-06-17

Description

Vulnerability in the Oracle Communications Convergence component of Oracle Communications Applications (subcomponent: Mail Proxy (dojo)). Supported versions that are affected are 3.0 and 3.0.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Communications Convergence. While the vulnerability is in Oracle Communications Convergence, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Communications Convergence accessible data as well as unauthorized read access to a subset of Oracle Communications Convergence accessible data. CVSS 3.0 Base Score 7.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N).

Frequently asked questions

What is CVE-2017-10031?: Vulnerability in the Oracle Communications Convergence component of Oracle Communications Applications (subcomponent: Mail Proxy (dojo)). Supported versions that are affected are 3.0 and 3.0.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Communications Convergence. While the vulnerability is in Oracle Communications Convergence, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Communications Convergence accessible data as well as unauthorized read access to a subset of Oracle Communications Convergence accessible data. CVSS 3.0 Base Score 7.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N).
How severe is CVE-2017-10031?: CVE-2017-10031 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2017-10031 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-10031?: CVE-2017-10031 primarily affects Oracle Communications Convergence. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-10031?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-10031 published?: CVE-2017-10031 was published on 2017-08-08 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:oracle:communications_convergence:3.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:communications_convergence:3.0.1:*:*:*:*:*:*:*

More vulnerabilities in Oracle Communications Convergence

CVE-2018-1000613 — Critical (CVSS 9.8): Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60…
CVE-2023-21848 — High (CVSS 8.8): Vulnerability in the Oracle Communications Convergence product of Oracle Communications Applications (component: Admin…
CVE-2020-28052 — High (CVSS 8.1): An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility…
CVE-2019-17359 — High (CVSS 7.5): The ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and…
CVE-2019-10086 — High (CVSS 7.3): In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for…
CVE-2019-10219 — Medium (CVSS 6.1): A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads…

All CVEs affecting Oracle Communications Convergence →