dbcve.org
Applications FrameworkApplication · Oracle

CVE-2022-21468

MEDIUM · 6.1 CVSS v3.1 Published 2022-04-19
Fix available
A fix is available. Upgrade to after 12.2.11 or later.
See remediation →
68/100
Remediation priority · Elevated
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 Applications Framework product of Oracle E-Business Suite (component: Popups). Supported versions that are affected are 12.2.4-12.2.11. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Applications Framework. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Applications Framework, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Applications Framework accessible data as well as unauthorized read access to a subset of Oracle Applications Framework accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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

Vulnerability in the Popups component of Oracle Applications Framework (part of Oracle E-Business Suite versions 12.2.4-12.2.11) allows unauthenticated attackers with network access via HTTP to read and modify some application data. Successful exploitation requires human interaction (such as tricking a user into clicking a malicious link).

MitigationApply Oracle Critical Patch Update (CPU) for April 2022 or later that addresses CVE-2022-21468. As interim mitigation, restrict network access to the Oracle Applications Framework and implement additional input validation on popup-related functions.

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
Applications FrameworkApplication
Affected:>= 12.2.4, <= 12.2.11

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 Applications Framework version
    Log into Oracle Applications Manager (OAM) and navigate to Oracle Applications Framework > Version Details, or query the FND_PRODUCT_INSTALLATIONS table to find the OAF version number
    Affected if The installed OAF version falls within 12.2.4 through 12.2.11 (inclusive)
  2. Confirm the Popups component is accessible
    Check if the /OA_HTML/popup or /OA_HTML/popups servlet paths are exposed and reachable in your OAF environment (these are the typical URL paths for the Popups functionality)
    Affected if The Popups servlet paths respond to HTTP requests, indicating the component is active
  3. Verify HTTP network exposure
    Determine if the Oracle Applications Framework web interfaces are accessible over HTTP/HTTPS from untrusted networks by reviewing web server configuration, load balancer rules, or firewall policies
    Affected if The OAF login page or popup servlets are reachable from network segments without proper access controls
  4. Check for recent security patches
    Query the Oracle AD patch applied patches (via adopmnctl.sh status or Oracle Enterprise Manager) or review the April 2022 CPU patch level applied to the environment
    Affected if The April 2022 Critical Patch Update (CPU) or later has NOT been applied, leaving the vulnerability unpatched

You are affected if your Oracle Applications Framework version is between 12.2.4 and 12.2.11, the Popups component is HTTP-accessible, and the April 2022 CPU or later has not been applied.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.11
Interim mitigation

Apply Oracle Critical Patch Update (CPU) for April 2022 or later that addresses CVE-2022-21468. As interim mitigation, restrict network access to the Oracle Applications Framework and implement additional input validation on popup-related functions.

Recommended fix High confidence

Apply Oracle Critical Patch Update April 2022 (or later CPU) to Oracle E-Business Suite 12.2.x

  1. Log into My Oracle Support and search for Oracle Critical Patch Update April 2022
  2. Locate the security patch for CVE-2022-21468 applicable to Oracle E-Business Suite 12.2.x
  3. Download and review the patch readme and prerequisites
  4. Apply the security patch following standard Oracle E-Business Suite patching procedures (using ADOP or applying patches manually)
  5. After applying the patch, verify the fix by confirming the patch is applied in the Oracle Applications Manager
  6. Test the Popups component functionality to ensure normal operation
Caveat Apply patches per Oracle standard procedures; follow all prerequisite steps to avoid issues with Oracle Applications Framework

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Applications Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21468 — 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-2022-21468 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