dbcve.org
IreceivablesApplication · Oracle

CVE-2017-3555

HIGH · 7.5 CVSS v3.0 Published 2017-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 iReceivables component of Oracle E-Business Suite (subcomponent: Self Registration). Supported versions that are affected are 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5 and 12.2.6. Easily "exploitable" vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle iReceivables. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle iReceivables. CVSS 3.0 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

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

A denial of service vulnerability exists in the Self Registration subcomponent of Oracle iReceivables (part of Oracle E-Business Suite). The flaw is remotely exploitable without authentication via HTTP, allowing an attacker to cause the service to hang or crash repeatedly.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for April 2017 that addresses CVE-2017-3555, or disable the Self Registration functionality in iReceivables if patching is not immediately feasible.

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
IreceivablesApplication
Affected:= 12.1.1= 12.1.2= 12.1.3= 12.2.3= 12.2.4= 12.2.5= 12.2.6

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

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

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 iReceivables version
    Query the Oracle E-Business Suite version using SQL: SELECT patch_level FROM applsys.ad_appl_patches WHERE patch_type = 'C'; or check the iReceivables patch level via OAM (Oracle Application Manager) or by reviewing installed patches.
    Affected if The installed version matches 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, or 12.2.6
  2. Verify Self Registration is enabled
    Log into Oracle iReceivables as a system administrator and navigate to the Self Registration configuration page (typically under Setup > System > Self Registration), or query the ICX_FUNCTIONS table for function_enabled_flag='Y' on the IGI_SELF_REGISTRATION function.
    Affected if Self Registration functionality is enabled in the iReceivables module
  3. Confirm HTTP access to Self Registration endpoint
    Attempt to access the Self Registration URL pattern for your EBS instance (commonly /OA_HTML/ibeCAcpSSO.jsp or similar endpoints under /OA_HTML/ with 'SelfRegistration' in the path), or check Apache/OHS web listener configuration for exposed iReceivables paths.
    Affected if The Self Registration web endpoint is accessible via HTTP without authentication
  4. Review for DoS indicators
    Check Oracle E-Business Suite diagnostic logs (specifically the JSP logs in $OA_HTML/logs or the concurrent request logs) and Apache error logs for repeated crashes or hang events related to the Self Registration component, or review ICX concurrent manager logs for failed Self Registration requests.
    Affected if Multiple crash, hang, or timeout events are logged for the Self Registration module

A user is affected if they run a vulnerable Oracle iReceivables version (12.1.1 through 12.2.6), have Self Registration enabled, and have the endpoint exposed via HTTP.

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 April 2017 that addresses CVE-2017-3555, or disable the Self Registration functionality in iReceivables if patching is not immediately feasible.

Fix this in Ireceivables Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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