E Business SuiteApplication · Oracle

CVE-2010-0861

MEDIUM · 5.0 CVSS v2.0 Published 2010-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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
Unspecified vulnerability in the Oracle HRMS (Self Service) component in Oracle E-Business Suite 11.5.10.2, 12.0.6, and 12.1.2 allows remote attackers to affect confidentiality via unknown vectors.

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

Oracle E-Business Suite HRMS (Self Service) contains an unspecified vulnerability allowing remote attackers to impact confidentiality. The vulnerability affects versions 11.5.10.2, 12.0.6, and 12.1.2 of the E-Business Suite. The exact attack vector and technical details are not disclosed in the vulnerability report.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for January 2010 or later. If the affected versions are no longer supported, upgrade to a supported Oracle E-Business Suite release line and ensure HRMS Self-Service is included in regular security patching cycles.

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
E Business SuiteApplication
Affected:= 11.5.10.2= 12.0.6= 12.1.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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/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 E-Business Suite version
    Query the database using SELECT release_name FROM apps.fnd_product_groups; or check the Oracle Applications context file (context_name.xml) in $INST_TOP/admin for the variable s.apps_version or similar version indicators.
    Affected if The installed version matches 11.5.10.2, 12.0.6, or 12.1.2 exactly.
  2. Confirm HRMS Self-Service module is present
    Query the Oracle E-Business Suite modules table (such as fnd_application_vl or icx_products) for HRMS-related product names like 'Human Resources Self Service' or 'SSHR' to determine if the HRMS Self-Service module is installed.
    Affected if HRMS Self-Service module is listed as installed or enabled in the product tables.
  3. Check if HRMS Self-Service is enabled for user access
    Review the Oracle E-Business Suite responsibility assignments through the Responsibilities form (蠣unctions/Security/Responsibility/Define) or query icx Responsibility tables to see if HRMS Self-Service responsibilities are assigned to any active users.
    Affected if Any HRMS Self-Service responsibilities exist and are assignable to users.
  4. Verify patch status for January 2010 CPU
    Check the applied patches using adpatch or by querying fnd_apply_installed_patches for CPUJAN2010 or subsequent critical patch updates. Alternatively, query fnd_product_installations to review recent security-related patches.
    Affected if The January 2010 Critical Patch Update or a later security patch has NOT been applied.

A user is affected if they run Oracle E-Business Suite version 11.5.10.2, 12.0.6, or 12.1.2 with HRMS Self-Service module enabled and have not applied the January 2010 or later CPU.

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 January 2010 or later. If the affected versions are no longer supported, upgrade to a supported Oracle E-Business Suite release line and ensure HRMS Self-Service is included in regular security patching cycles.

Fix this in E Business Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2010-0861 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