Authenticated access to and alteration of payment data
Published Jan 15, 2020 · Updated Sep 30, 2024
Unspecified flaw in Oracle Banking Payments 14.1.0 through 14.3.0 allows remote authenticated users to read and alter payment data via HTTP. Oracle identifies the affected locus only as the Core component and has not published the erroneous operation or input that triggers it. Low-privilege credentials are required; successful exploitation grants broad data access and limited insertion, update, or deletion rights.
Summary
What happened
Unspecified flaw in Oracle Banking Payments 14.1.0 through 14.3.0 allows remote authenticated users to read and alter payment data via HTTP. Oracle identifies the affected locus only as the Core component and has not published the erroneous operation or input that triggers it. Low-privilege credentials are required; successful exploitation grants broad data access and limited insertion, update, or deletion rights.
The record
- CVE
- CVE-2020-2713
- Published
- Jan 15, 2020
- Updated
- Sep 30, 2024
- Vendor
- Oracle Corporation
- Product
- Oracle Banking Payments
- Classifications
- T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 15, 2020CVE publishedPublication date reported by the CVE source.
- Sep 30, 2024Record 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=14.1.0-14.3.0
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
No public exploit references are available in this record.
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