CVE-2021-2099
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 CRM Technical Foundation product of Oracle E-Business Suite (component: Preferences). Supported versions that are affected are 12.2.3-12.2.10. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle CRM Technical Foundation. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle CRM Technical Foundation, 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 CRM Technical Foundation accessible data as well as unauthorized update, insert or delete access to some of Oracle CRM Technical Foundation 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 confidenceUnauthenticated reflected XSS vulnerability in Oracle CRM Technical Foundation's Preferences component. Attackers can inject malicious scripts via HTTP requests that execute in victim browsers when they interact with crafted links, potentially exposing sensitive data or performing unauthorized actions.
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.2.3, <= 12.2.10CVSS 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 Oracle E-Business Suite versionLocate the Oracle E-Business Suite installation directory and check the version file, typically found in $ORACLE_HOME/../. The version can also be retrieved via SQL query: SELECT release_name FROM apps.fnd_product_groups;Affected if The version returned is between 12.2.3 and 12.2.10 inclusive
-
Verify CRM Technical Foundation componentConfirm the CRM Technical Foundation component is installed by checking the Oracle Applications Manager (OAM) or via SQL: SELECT component_name, version FROM apps.fnd_installed_components WHERE component_name LIKE '%CRM Technical Foundation%';Affected if The component is present and matches the version range in step 1
-
Confirm Preferences web module is accessibleCheck if the Preferences functionality is exposed via web by attempting to access the endpoint URL pattern typically at /OA_HTML/xx/ieb/preferences.jsp or /OA_HTML/ personalization. The exact path varies by configuration; check Oracle HTTP Server access logs for requests to the Preferences servlet.Affected if The Preferences component is accessible over HTTP without authentication
-
Examine HTTP access logs for XSS indicatorsReview Oracle HTTP Server access logs (typically in $ORACLE_HOME/../iAS/Apache/logs/) for reflected XSS patterns in requests to the Preferences endpoint. Search for suspicious query parameters containing script tags like <script>, javascript:, or event handlers like onerror, onload.Affected if Log entries show unauthenticated HTTP requests with XSS payloads targeting the Preferences component URL pattern
You are affected if Oracle E-Business Suite with CRM Technical Foundation is installed with a version between 12.2.3 and 12.2.10 and the Preferences component is accessible via the web 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 Oracle Critical Patch Update (CPU) January 2021 that addresses CVE-2021-2099; until patched, configure WAF rules to filter malicious payloads in HTTP requests to the Preferences component.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2099 — 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-2099 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