CVE-2021-2080
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 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 confidenceOracle Configurator UI Servlet contains an unauthenticated remote vulnerability allowing network attackers via HTTP to achieve high confidentiality impact (full data access) and moderate integrity impact (partial data modification). The attack requires human interaction, reducing exploit automation potential but not severity impact.
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= 12.1= 12.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Oracle Configurator is installedCheck your Oracle Applications environment for the presence of Oracle Configurator component. This is typically part of Oracle E-Business Suite. Look for configurator-related application directories, patches, or components in your Oracle inventory.Affected if Oracle Configurator is not present in the environment, the system is not affected.
-
Determine the installed Oracle Configurator versionQuery the Oracle Configurator version using SQL against the Oracle E-Business Suite version tables, or check the about page/logs of the Configurator UI application. Compare your installed version against 12.1 and 12.2.Affected if The installed version is exactly 12.1 or exactly 12.2, the system falls within the affected range.
-
Verify the UI Servlet component is accessibleIdentify if the Oracle Configurator UI Servlet endpoint is exposed and reachable via HTTP/HTTPS. This is typically accessed through the Oracle Application Server or Oracle HTTP Server. Check web server configurations for configurator-related URL paths.Affected if The UI Servlet is exposed and accessible over the network without authentication.
-
Check if HTTP access is unauthenticatedReview the web server or Oracle WebLogic/Oracle HTTP Server configuration to determine whether the Configurator UI Servlet endpoint requires authentication, or attempt a request to the servlet URL without providing credentials.Affected if The UI Servlet can be accessed via HTTP without any authentication credentials.
-
Assess network accessibilityDetermine if the Oracle Configurator UI Servlet is accessible from the network. Check firewall rules, Oracle WebGate configuration, and whether the application is exposed to internal or external networks.Affected if The vulnerable servlet is network-accessible and accepts HTTP requests from untrusted sources.
The environment is affected if Oracle Configurator versions 12.1 or 12.2 are installed AND the UI Servlet is network-accessible without authentication.
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 relevant Oracle Critical Patch Update (CPU) for CVE-2021-2080 to Oracle Configurator versions 12.1 and 12.2, or upgrade to a patched version if available from Oracle support.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2080 — 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-2021-2080 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