E Business SuiteApplication · Oracle

CVE-2010-0077

MEDIUM · 6.4 CVSS v2.0 Published 2010-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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 CRM Technical Foundation (mobile) component in Oracle E-Business Suite 11.5.10.2, 12.0.6, and 12.1.2 allows remote attackers to affect confidentiality and integrity 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

A vulnerability in Oracle E-Business Suite's CRM Technical Foundation mobile component allows remote attackers to impact confidentiality and integrity. The specific attack vector and technical details are unspecified in available documentation, but the CVSS 6.4 indicates network-exploitable access with partial impact on data without authentication.

MitigationApply Oracle Critical Patch Updates for the affected E-Business Suite versions (11.5.10.2, 12.0.6, 12.1.2), or upgrade to a supported version. Given the age of these versions (2010), a comprehensive upgrade path assessment is recommended.

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
Partial
Availability
None

AV:N/AC:L/Au:N/C:P/I:P/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 installed version
    Query the FND_PRODUCT_INSTALLATIONS table using SQL: SELECT APPLICATION_ID, APPLICATION_NAME, PATCH_LEVEL FROM FND_PRODUCT_INSTALLATIONS WHERE APPLICATION_SHORT_NAME = 'FND'; Or use the adident utility: adident Header $FND_TOP/ls/AfEBSDB.pls
    Affected if The version returned is 11.5.10.2, 12.0.6, or 12.1.2 exactly as listed in the affected versions
  2. Check if CRM Technical Foundation component is installed
    Query the FND_APPLICATION table: SELECT APPLICATION_ID, APPLICATION_SHORT_NAME, APPLICATION_NAME FROM FND_APPLICATION WHERE APPLICATION_SHORT_NAME IN ('FND','FTE','FCT','FSC'); These are related CRM Technical Foundation modules. Also check for MOBILE component presence in FND_PRODUCT_GROUPS or equivalent.
    Affected if The CRM Technical Foundation component (application ID typically in the 100-200 range for FND-related modules) shows as installed in the E-Business Suite instance
  3. Verify if mobile web interface is enabled
    Check the Oracle E-Business Suite context file (typically in $INST_TOP/appl/admin/ context_name.xml) for mobile-related configurations. Look for entries containing 'mobile' or 'MOBILE' in the s_serverparameter or s_web_adjunct parameters. Alternatively query ICX_PARAMETERS for mobile-related session parameters.
    Affected if The mobile web interface or mobile servlet is enabled and accessible (servlet name typically includes 'mobile' or 'MSM' in the configuration)
  4. Check for unauthenticated access to mobile endpoints
    Review the web logic or Apache configuration for the E-Business Suite middle tier. Identify mobile servlet endpoints (commonly /MSM/* or /OA_HTML/mobile/*). Test if these endpoints respond without authentication by accessing the base URL with paths like /OA_HTML/msc or checking if the mobile login page is publicly accessible.
    Affected if The mobile CRM endpoints are exposed and accessible without authentication (CVSS indicates no authentication required for exploitation)

A user is affected if their Oracle E-Business Suite version matches 11.5.10.2, 12.0.6, or 12.1.2 AND the CRM Technical Foundation mobile component is installed and exposed.

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 Oracle Critical Patch Updates for the affected E-Business Suite versions (11.5.10.2, 12.0.6, 12.1.2), or upgrade to a supported version. Given the age of these versions (2010), a comprehensive upgrade path assessment is recommended.

Fix this in E Business Suite Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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