Application Object LibraryApplication · Oracle

CVE-2024-20915

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-17

Fix available

A fix is available. Upgrade to after 12.2.13 or later.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Vulnerability in the Oracle Application Object Library product of Oracle E-Business Suite (component: Login - SSO). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Application Object Library. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Application Object Library. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Technical summary

dbcve analysis · high confidence

An unauthenticated attacker can cause a partial denial of service in Oracle Application Object Library's SSO login component by sending crafted HTTP requests. The vulnerability affects Oracle E-Business Suite versions 12.2.3 through 12.2.13, with successful attacks resulting in low-impact availability disruption.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for CVE-2024-20915 to Oracle E-Business Suite installations, ensuring regression testing of SSO authentication is performed in a non-production environment before production deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Application Object LibraryApplication

Affected:>= 12.2.3, <= 12.2.13

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Oracle E-Business Suite installation

Run the command 'adident utilities' or check the Oracle application tier for E-Business Suite installation directories (typically $ORACLE_HOME/apps). Alternatively, query the database for the version using: SELECT release_name FROM apps.fnd_product_groups;

Affected if No Oracle E-Business Suite installation is found - not affected.
Determine Application Object Library version

Check the version of Oracle Application Object Library by querying: SELECT a.application_name, b.release_name FROM apps.fnd_application a, apps.fnd_product_installations b WHERE a.application_id = b.application_id AND a.application_short_name = 'FND'; Or check the 'release_name' in the environment or patch level files.

Affected if The version is outside the range 12.2.3 to 12.2.13 - not affected.
Verify SSO login component is enabled

Check if Oracle E-Business Suite SSO is configured by reviewing the Oracle Internet Directory (OID) integration, checking the $IAS_ORACLE_HOME/Apache/modose.conf or $ORACLE_HOME/tech_st/weboh/ohs/conf/httpd.conf for SSO-related directives, or query: SELECT parameter_value FROM apps.icx_parameters WHERE parameter_name LIKE '%SSO%';

Affected if SSO is not enabled or not configured - likely not affected since the vulnerability is in the SSO login component.
Review SSO component patch level

Check the Oracle Application Object Library patch level by running 'adpatch' logs or querying: SELECT patch_level FROM apps.fnd_product_installations WHERE application_id = (SELECT application_id FROM apps.fnd_application WHERE application_short_name = 'FND'); Compare against Oracle patch database for CVE-2024-20915 patches.

Affected if The installed patches do not include the CVE-2024-20915 fix - potentially affected.
Inspect HTTP access logs for suspicious SSO requests

Review web server access logs (in $ORACLE_HOME/tech_st/weboh/ohs/logs or $IAS_ORACLE_HOME/Apache/access_log) for unusual patterns in /OA_HTML/AppsLogin or /sso/authup or similar SSO endpoints, such as high volumes of requests from single IPs or malformed parameters.

Affected if Anomalous SSO login request patterns are detected - may indicate exploitation attempts.

A user is affected if they have Oracle E-Business Suite version 12.2.3 through 12.2.13 with SSO login component enabled and without the CVE-2024-20915 patch applied.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.13

Interim mitigation

Apply the relevant Oracle Critical Patch Update (CPU) for CVE-2024-20915 to Oracle E-Business Suite installations, ensuring regression testing of SSO authentication is performed in a non-production environment before production deployment.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update (CPU) for January 2024, which contains the fix for CVE-2024-20915
Contact Oracle Support to obtain the specific patch number for your Oracle E-Business Suite 12.2.x release
Download and apply the patch following Oracle's standard patch application procedures for EBS
After patching, verify the Login - SSO functionality works correctly and the vulnerability is remediated
Consult Oracle Support documentation for any required post-patch steps or additional requirements

Caveat Oracle EBS patches may require downtime and should be tested in a non-production environment before production deployment; patches are cumulative so apply the latest available CPU for your release

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

Fix this in Application Object Library Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing6.0 h
Review / QA2.0 h

15.0 hours of engineering $2,580

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20915 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-20915?

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.

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

At a glance

A fix existsUpgrade to after 12.2.13 or later

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Application Object Library

Remediation

Need this fixed?

Fix this in Application Object Library 15 hrs · Moderate

Typical engagement from $2,580

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-20915 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References