dbcve.org
ConfiguratorApplication · Oracle

CVE-2021-2079

HIGH · 8.2 CVSS v3.1 Published 2021-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Vulnerability in the Oracle Configurator product of Oracle Supply Chain (component: UI Servlet). Supported versions that are affected are 12.1 and 12.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Configurator. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Configurator, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Configurator accessible data as well as unauthorized update, insert or delete access to some of Oracle Configurator accessible data. CVSS 3.1 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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 confidence

Unauthenticated HTTP vulnerability in the UI Servlet component of Oracle Configurator (versions 12.1, 12.2) allows remote attackers to gain unauthorized access to critical data or perform unauthorized updates/inserts/deletes. The attack requires human interaction and can impact additional products due to scope change.

MitigationApply Oracle Critical Patch Update (CPU) for Oracle Configurator addressing the UI Servlet vulnerability in versions 12.1 and 12.2; restrict network exposure of the Configurator UI servlets to trusted users only as an interim control.

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
ConfiguratorApplication
Affected:= 12.1= 12.2

CVSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Configurator installation
    Check for Oracle Configurator web application by reviewing deployed applications in Oracle WebLogic Server or Oracle HTTP Server, or look for configurator-related processes and paths in the Oracle E-Business Suite environment
    Affected if Oracle Configurator is deployed and running in the environment
  2. Verify installed version
    Query the Oracle Configurator version through the application's About page, Oracle Application Manager, or by checking the installation directory for version manifests. Compare against affected versions 12.1 and 12.2
    Affected if Installed version is exactly 12.1 or 12.2
  3. Confirm UI Servlet component is accessible
    Attempt to access the UI Servlet endpoint - typical paths include /configurator/UiServlet or /oa_servlets/oracle.apps.cz.UiServlet - via HTTP/HTTPS from a browser or curl command
    Affected if The UI Servlet endpoint responds with any HTTP status code (200, 401, 403, etc.) indicating the service is exposed
  4. Test unauthenticated access to UI Servlet
    Send an HTTP request to the UI Servlet path without providing any authentication credentials (session cookie, OAM token, or SSO token)
    Affected if The servlet returns HTTP 200 or allows access without requiring valid authentication
  5. Check network exposure of Configurator servlets
    Review firewall rules, Oracle WebGate/OAM policies, and load balancer access controls to determine if the configurator UI servlets are accessible from untrusted networks or the internet
    Affected if Servlets are reachable from networks outside trusted user populations

User is affected if Oracle Configurator versions 12.1 or 12.2 are installed AND the UI Servlet component is exposed to untrusted network paths without authentication enforcement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) for Oracle Configurator addressing the UI Servlet vulnerability in versions 12.1 and 12.2; restrict network exposure of the Configurator UI servlets to trusted users only as an interim control.

Fix this in Configurator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-2079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-2079 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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