CVE-2018-3027
Last modified
CVE-2018-3027 is a vulnerability of currently unknown severity. Vulnerability in the Oracle Banking Payments component of Oracle Financial Services Applications (subcomponent: Payments Core). Supported versions that are affected are 12.2.0, 12.3.0, 12.4.0, 12.5.0 and 14.1.0. EPSS estimates a 2.03% chance of exploitation in the next 30 days.
Description
Vulnerability in the Oracle Banking Payments component of Oracle Financial Services Applications (subcomponent: Payments Core). Supported versions that are affected are 12.2.0, 12.3.0, 12.4.0, 12.5.0 and 14.1.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Payments. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Banking Payments accessible data as well as unauthorized access to critical data or complete access to all Oracle Banking Payments accessible data. CVSS 3.0 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Oracle | Banking Payments | 12.2.0 |
| Oracle | Banking Payments | 12.3.0 |
| Oracle | Banking Payments | 12.4.0 |
| Oracle | Banking Payments | 12.5.0 |
| Oracle | Banking Payments | 14.1.0 |
References
- http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/104790Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1041307Third Party Advisory, VDB Entry
- http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/104790Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1041307Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-3027?
How severe is CVE-2018-3027?
How do I fix CVE-2018-3027?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-3021Vulnerability in the Oracle Banking Payments component of Or…
- CVE-2018-3022Vulnerability in the Oracle Banking Payments component of Or…
- CVE-2018-3023Vulnerability in the Oracle Banking Payments component of Or…
- CVE-2018-3024Vulnerability in the Oracle Banking Payments component of Or…
- CVE-2018-3025Vulnerability in the Oracle Banking Payments component of Or…
- CVE-2018-3026Vulnerability in the Oracle Banking Payments component of Or…
- CVE-2018-3028Vulnerability in the Oracle FLEXCUBE Investor Servicing comp…
- CVE-2018-3029Vulnerability in the Oracle FLEXCUBE Investor Servicing comp…
- CVE-2018-3030Vulnerability in the Oracle FLEXCUBE Investor Servicing comp…
- CVE-2018-3031Vulnerability in the Oracle FLEXCUBE Investor Servicing comp…
- CVE-2018-3032Vulnerability in the Oracle FLEXCUBE Investor Servicing comp…
- CVE-2018-3033Vulnerability in the Oracle FLEXCUBE Investor Servicing comp…
Are you affected by CVE-2018-3027?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
