dbcve.org
Reports DeveloperApplication · Oracle

CVE-2024-21133

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Reports Developer product of Oracle Fusion Middleware (component: Servlet). Supported versions that are affected are 12.2.1.4.0 and 12.2.1.19.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Reports Developer. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Reports Developer, 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 Reports Developer accessible data as well as unauthorized read access to a subset of Oracle Reports Developer 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 · moderate confidence

Unauthenticated HTTP servlet vulnerability in Oracle Reports Developer allowing remote attackers with human interaction to achieve partial read and write access to application data. The CVSS vector indicates a scope change affecting additional products and requires user interaction (likely clicking a malicious link).

MitigationApply Oracle Critical Patch Update addressing CVE-2024-21133; if patching is not immediately feasible, restrict network access to Oracle Reports Developer endpoints and implement CSRF protections for state-changing operations.

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
Reports DeveloperApplication
Affected:= 12.2.1.4.0= 12.2.1.19.0

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. Confirm Oracle Reports Developer is installed
    Locate the Oracle Reports Developer installation directory and identify the product. Common paths include $ORACLE_HOME/reports or check for reports.jar files. Use 'opatch lsinventory' or check the Oracle Inventory for installed products.
    Affected if The product Oracle Reports Developer is present on the system
  2. Check the installed version number
    Run 'opatch lsinventory' or inspect the version file in the Oracle Reports Developer home directory. Look for version strings 12.2.1.4.0 or 12.2.1.19.0 specifically.
    Affected if The installed version is exactly 12.2.1.4.0 or exactly 12.2.1.19.0
  3. Verify HTTP servlet interface is enabled
    Check the Oracle Reports Server configuration file (typically rep_winserver.conf, reports.conf, or rwservlet.properties) for servlet mappings. Look for rwservlet or reports servlet entries that expose HTTP endpoints.
    Affected if HTTP servlet endpoints (rwservlet) are configured and enabled in the Reports Server configuration
  4. Determine if Reports is network accessible
    Check listener configuration (listener.ora) and verify if the Reports HTTP port is exposed to network interfaces rather than localhost only. Inspect ORACLE_HTTP_SERVER ports in the configuration.
    Affected if The Reports HTTP servlet is listening on a network-accessible interface (not localhost/127.0.0.1 only)
  5. Check for user-facing web exposure
    Review Oracle WebTier or Oracle HTTP Server configuration to determine if Reports servlet is accessible via browser. Look for /reports/* or /rwservlet/* URL mappings in the web server configuration.
    Affected if The servlet is accessible through a web server to end users who could click malicious links

You are affected if Oracle Reports Developer version 12.2.1.4.0 or 12.2.1.19.0 is installed with HTTP servlet functionality exposed to network users who could be tricked into clicking a malicious link.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update addressing CVE-2024-21133; if patching is not immediately feasible, restrict network access to Oracle Reports Developer endpoints and implement CSRF protections for state-changing operations.

Recommended fix Moderate confidence

Apply the Oracle quarterly security patch that addresses CVE-2024-21133 for Reports Developer 12.2.1.4.0 or 12.2.1.19.0

  1. 1. Review Oracle's Critical Patch Update advisory for the quarter containing the fix for CVE-2024-21133
  2. 2. Identify the specific patch number for Oracle Reports Developer from Oracle's patch documentation
  3. 3. Apply the relevant quarterly security patch from Oracle's My Oracle Support
  4. 4. Test the patched environment to verify the XSS vulnerability is remediated
  5. 5. Verify that Oracle Reports Developer functionality remains intact after patching
Caveat Standard risk associated with applying Oracle middleware patches - test in non-production environment first

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

Fix this in Reports Developer 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-2024-21133 — 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-2024-21133 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