Infosphere Optim Data Growth For Oracle E Business SuiteDatabase / datastore · Ibm

CVE-2013-2956

HIGH · 7.5 CVSS v2.0 Published 2013-05-27
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
SQL injection vulnerability in the Console in IBM InfoSphere Optim Data Growth for Oracle E-Business Suite 6.x, 7.x, and 9.x before 9.1.0.3 allows remote attackers to execute arbitrary SQL commands via unspecified 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 · high confidence

SQL injection vulnerability in the Console component of IBM InfoSphere Optim Data Growth for Oracle E-Business Suite allows remote attackers to execute arbitrary SQL commands. The vulnerability affects versions 6.x, 7.x, and 9.x prior to 9.1.0.3. Attackers can exploit unspecified vectors in the console interface to inject malicious SQL statements.

MitigationUpgrade to IBM InfoSphere Optim Data Growth for Oracle E-Business Suite version 9.1.0.3 or later. Apply vendor-supplied patches if available for earlier supported versions.

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
Infosphere Optim Data Growth For Oracle E Business SuiteDatabase / datastore
Affected:= 6.0= 6.1= 6.3.1= 6.3.2= 6.3.3= 6.4.0= 6.4.1= 6.5.0= 6.5.1= 7.1.0= 7.1.1= 7.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
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 if IBM InfoSphere Optim is installed
    Look for the product installation directory (commonly under /opt/IBM/Optim or C:\Program Files\IBM\Optim on Windows). Check for the 'Optim' product folder and subfolders named 'DataGrowth' or 'OracleEBS'.
    Affected if The product is not installed - no action needed. If found, proceed to version check.
  2. Determine the installed version
    Check the version information in the installation directory. Look for a version file, manifest, or product info in the main Optim directory. On Windows, check Add/Remove Programs for the exact version string. Common paths: <install_dir>/optim/versions.txt or <install_dir>/version.ini.
    Affected if The installed version matches 6.0, 6.1, 6.3.1, 6.3.2, 6.3.3, 6.4.0, 6.4.1, 6.5.0, 6.5.1, 7.1.0, 7.1.1, 7.1.2, or any 9.x version prior to 9.1.0.3 - the system is potentially affected.
  3. Check if Console component is exposed
    Identify if the Optim Console web interface is running and accessible. Check for listening ports (common ports 8080, 8443, or custom ports configured during installation). Use 'netstat -an' or equivalent to find processes listening on HTTP/HTTPS ports associated with Optim.
    Affected if The Console web interface is exposed on a network-accessible port without proper authentication restrictions - the system is vulnerable to remote SQL injection.
  4. Verify Console authentication settings
    Review the Console configuration files (typically in <install_dir>/console/conf or <install_dir>/webservices/conf) for authentication settings. Check if the console allows unauthenticated or weakly authenticated access.
    Affected if The Console permits unauthenticated access or uses default credentials - the SQL injection vulnerability is exploitable.

You are affected if IBM InfoSphere Optim Data Growth for Oracle E-Business Suite is installed with any version from 6.0 through 7.1.2, or 9.x versions before 9.1.0.3, and the Console component is network-accessible.

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

Upgrade to IBM InfoSphere Optim Data Growth for Oracle E-Business Suite version 9.1.0.3 or later. Apply vendor-supplied patches if available for earlier supported versions.

Fix this in Infosphere Optim Data Growth For Oracle E Business Suite 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-2013-2956 — 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-2013-2956 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