CVE-2021-2092
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.1.3 and 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 vulnerability in Oracle E-Business Suite CRM Technical Foundation Preferences component allows remote attackers via HTTP to access critical data and perform unauthorized updates/inserts/deletes. Exploitation requires human interaction (likely social engineering/phishing), and while the vulnerability is in one component, attacks may impact additional products due to scope change.
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.10= 12.1.3CVSS 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 versionQuery the database for the current EBS version by running 'select release_version from fnd_product_groups;' or check the OAM (Oracle Application Manager) dashboard for the CRM Technical Foundation version.Affected if The version falls outside the safe ranges (not 12.1.3 and not between 12.2.3 and 12.2.10). Versions below 12.1.3 or above 12.2.10 are not listed as affected.
-
Confirm CRM Technical Foundation component is installedCheck if the CRM Technical Foundation component is present in the EBS instance by reviewing the applied patches via 'adutlqrq.sql' or checking the Oracle Applications Manager (OAM) -> Site Map -> Oracle Applications Manager -> Applied Patches.Affected if The CRM Technical Foundation component is not installed or not active - if the component is absent, the specific vulnerability in that component does not apply.
-
Verify HTTP access is enabled for the Preferences functionReview the Oracle E-Business Suite profile options and function security settings. Check if the 'FND_FUNCTION' for 'FND_PREFS' (Preferences) is exposed through Oracle Application Framework (OAF) pages accessible via HTTP. Query 'SELECT function_name FROM fnd_form_functions WHERE function_name LIKE '%PREF%';' to identify exposed preference-related functions.Affected if The Preferences component is accessible via HTTP without proper authentication guards - if the function is exposed through ICX or OAF pages accessible externally, the vulnerability can be exploited.
-
Check for recent security patchesReview the applied Oracle patches using 'adutlqrq.sql' or by querying 'SELECT patch_name, creation_date FROM ad_bugs WHERE patch_name LIKE '%CR%' ORDER BY creation_date DESC;' to identify if CPU patches from January 2021 or later have been applied.Affected if The January 2021 CPU (or subsequent updates) containing the fix for CVE-2021-2092 has NOT been applied.
A user is affected if their Oracle E-Business Suite runs version 12.1.3 or any version between 12.2.3 and 12.2.10, has the CRM Technical Foundation Preferences component exposed via HTTP, and lacks the January 2021 Critical Patch Update.
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) containing the fix for CVE-2021-2092. Since human interaction is required for exploitation, implement user security awareness training to reduce phishing success.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2092 — 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-2092 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