dbcve.org
Commerce PlatformApplication · Oracle

CVE-2022-21387

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Commerce Platform product of Oracle Commerce (component: Dynamo Application Framework). Supported versions that are affected are 11.3.0, 11.3.1 and 11.3.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Commerce Platform. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Commerce Platform accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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

Oracle Commerce Platform's Dynamo Application Framework contains an information disclosure vulnerability allowing unauthenticated attackers with network access via HTTP to read a subset of accessible data. The flaw affects versions 11.3.0, 11.3.1, and 11.3.2, with CVSS 3.1 scoring 5.3 indicating low confidentiality impact without integrity or availability compromise.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for CVE-2022-21387 or upgrade to a patched version of Oracle Commerce Platform. If immediate patching is not feasible, implement a Web Application Firewall (WAF) to filter malicious HTTP requests targeting the Dynamo Application Framework.

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
Commerce PlatformApplication
Affected:= 11.3.0= 11.3.1= 11.3.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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Commerce Platform installation
    Search for Oracle Commerce Platform components in your environment. Check application server configurations (WebLogic, etc.) for Oracle Commerce deployments. Look for directories or services named 'atg' or 'dynamo' which are typical Oracle Commerce markers.
    Affected if Oracle Commerce Platform is installed and running on the system
  2. Determine the installed version of Oracle Commerce Platform
    Check the version file or deployment descriptor within the Oracle Commerce installation directory. Common locations include version.properties, manifest files, or the root directory of the Commerce deployment. Compare the found version against 11.3.0, 11.3.1, or 11.3.2.
    Affected if The installed version matches exactly 11.3.0, 11.3.1, or 11.3.2
  3. Verify Dynamo Application Framework is accessible
    Confirm the Dynamo Application Framework endpoints are exposed and reachable via HTTP. Check if the /dyn/ or similar Dynamo-related URL paths are accessible on the application server. Review servlet and filter configurations in the web.xml deployment descriptor.
    Affected if The Dynamo Application Framework is enabled and exposed via HTTP network access
  4. Assess network exposure
    Determine if the Oracle Commerce application is accessible over the network via HTTP/HTTPS from untrusted sources. Review firewall rules, load balancer configurations, and network ACLs that permit inbound HTTP traffic to the Commerce Platform ports.
    Affected if The application is accessible via HTTP from untrusted network locations without proper access controls

A system is affected if it runs Oracle Commerce Platform versions 11.3.0, 11.3.1, or 11.3.2 with the Dynamo Application Framework exposed to network access, allowing unauthenticated HTTP requests to potentially read accessible data.

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 the relevant Oracle Critical Patch Update (CPU) for CVE-2022-21387 or upgrade to a patched version of Oracle Commerce Platform. If immediate patching is not feasible, implement a Web Application Firewall (WAF) to filter malicious HTTP requests targeting the Dynamo Application Framework.

Fix this in Commerce Platform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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