CVE-2020-14709
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability in the Customer Management and Segmentation Foundation product of Oracle Retail Applications (component: Card). Supported versions that are affected are 16.0, 17.0 and 18.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Customer Management and Segmentation Foundation. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Customer Management and Segmentation Foundation accessible data as well as unauthorized read access to a subset of Customer Management and Segmentation Foundation accessible data. CVSS 3.1 Base Score 7.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVulnerability in Oracle Retail Customer Management and Segmentation Foundation's Card component allows low-privileged authenticated attackers with network access via HTTP to create, delete, or modify critical data, as well as read a subset of accessible data. The attack is easily exploitable given the low complexity and no user interaction required.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 16.0= 17.0= 18.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Oracle Retail Customer Management and Segmentation Foundation is installedReview installed software inventory or application listings for Oracle Retail Customer Management and Segmentation FoundationAffected if The product is present in the environment
-
Determine the installed versionCheck the application version through its admin console, About page, or version lookup command specific to the Oracle Retail installationAffected if The version is exactly 16.0, 17.0, or 18.0
-
Locate the Card component endpointIdentify if HTTP-accessible endpoints related to Card functionality exist (typically under paths containing /card/ or Card-related servlets)Affected if The Card component is exposed via HTTP and accessible over the network
-
Verify network accessibility of the Card componentTest HTTP access to the Card component endpoint from external network positions or confirm the service listens on accessible network interfacesAffected if The Card HTTP endpoint is reachable from network locations where low-privileged users operate
-
Check authentication configurationReview the Card component's authentication settings to determine if low-privileged or unauthenticated access is possibleAffected if Low-privileged authenticated users or anonymous access can reach the Card component HTTP interface
A user is affected if Oracle Retail Customer Management and Segmentation Foundation versions 16.0, 17.0, or 18.0 are installed and the Card component is exposed via HTTP with accessible network paths.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the Oracle Critical Patch Update (or applicable security patch) for CVE-2020-14709. Until patched, restrict network access to the affected HTTP endpoints and implement WAF rules to detect anomalous Card component requests.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14709 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data