How severe is CVE-2017-3254?

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

Is CVE-2017-3254 being actively exploited?

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

What products are affected by CVE-2017-3254?

CVE-2017-3254 primarily affects Oracle Retail Invoice Matching. 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-3254?

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-3254 published?

CVE-2017-3254 was published on 2017-04-24 and last updated on 2026-06-17.

CVE-2017-3254

CVE-2017-3254 is a high-severity vulnerability in Oracle Retail Invoice Matching with a CVSS 3.x base score of 7.6. 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.6)
CVSS v2: 8.3
EPSS exploit prediction: 1% (71st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Retail Invoice Matching
Published: 2017-04-24
Last modified: 2026-06-17

Description

Vulnerability in the Oracle Retail Invoice Matching component of Oracle Retail Applications (subcomponent: Security). Supported versions that are affected are 12.0 and 13.0. Easily "exploitable" vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Retail Invoice Matching. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Retail Invoice Matching accessible data as well as unauthorized update, insert or delete access to some of Oracle Retail Invoice Matching accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Retail Invoice Matching. CVSS 3.0 Base Score 7.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L).

Frequently asked questions

What is CVE-2017-3254?: Vulnerability in the Oracle Retail Invoice Matching component of Oracle Retail Applications (subcomponent: Security). Supported versions that are affected are 12.0 and 13.0. Easily "exploitable" vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Retail Invoice Matching. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Retail Invoice Matching accessible data as well as unauthorized update, insert or delete access to some of Oracle Retail Invoice Matching accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Retail Invoice Matching. CVSS 3.0 Base Score 7.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L).
How severe is CVE-2017-3254?: CVE-2017-3254 has a CVSS 3.x base score of 7.6, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity low, and availability low.
Is CVE-2017-3254 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (71st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-3254?: CVE-2017-3254 primarily affects Oracle Retail Invoice Matching. 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-3254?: 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-3254 published?: CVE-2017-3254 was published on 2017-04-24 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:oracle:retail_invoice_matching:12.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:retail_invoice_matching:13.0:*:*:*:*:*:*:*

More vulnerabilities in Oracle Retail Invoice Matching

CVE-2017-12617 — High (CVSS 8.1): When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with…
CVE-2018-15756 — High (CVSS 7.5): Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported…
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-2020-5421 — Medium (CVSS 6.5): In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported…
CVE-2019-10219 — Medium (CVSS 6.1): A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads…
CVE-2019-17091 — Medium (CVSS 6.1): faces/context/PartialViewContextImpl.java in Eclipse Mojarra, as used in Mojarra for Eclipse EE4J before 2.3.10 and…

All CVEs affecting Oracle Retail Invoice Matching →