Infosphere Information ServerApplication · Ibm

CVE-2012-0705

HIGH · 7.1 CVSS v2.0 Published 2013-01-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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
InfoSphere Import Export Manager in InfoSphere Information Server MetaBrokers & Bridges (MBB) in IBM InfoSphere Information Server 8.1, 8.5 before FP3, 8.7, and 9.1 does not validate unspecified input data, which allows remote authenticated users to execute arbitrary commands 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

IBM InfoSphere Import Export Manager in MetaBrokers & Bridges fails to validate input data, allowing remote authenticated users to execute arbitrary commands through unspecified vectors. This is a command injection vulnerability requiring valid authentication.

MitigationApply IBM InfoSphere Information Server fixes: upgrade to 8.5 FP3 or later, or apply the relevant interim fix/APAR for affected versions. Implement strict input validation on the Import Export Manager component.

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 Information ServerApplication
Affected:= 8.1= 8.5= 8.5.0.1= 8.5.0.2= 8.7= 9.1
Infosphere Information Server Metabrokers \& BridgesApplication
Affected:all versions

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
High
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:H/Au:S/C:C/I:C/A:C

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. Verify IBM InfoSphere Information Server installation
    Locate the IBM InfoSphere Information Server installation directory and check for presence of the product. Common locations include /opt/IBM/InformationServer or C:\Program Files\IBM\InformationServer. Look for istool or dsjob commands in the bin directory.
    Affected if The product is installed in any version from 8.1 through 9.1, or if MetaBrokers & Bridges components are present regardless of version.
  2. Determine the installed version of IBM InfoSphere Information Server
    Run the version command for the installation, typically via 'isversion' or by examining version files in the installation directory. Check the version against the affected list: 8.1, 8.5, 8.5.0.1, 8.5.0.2, 8.7, or 9.1.
    Affected if The installed version matches any of the affected versions listed.
  3. Confirm Import Export Manager component is present
    Check for the Import Export Manager module within the IBM InfoSphere Information Server installation. This is typically found under the tools or modules directory. Look for components related to data import/export functionality.
    Affected if Import Export Manager component is installed and available on the system.
  4. Verify MetaBrokers & Bridges installation
    Check for the presence of MetaBrokers & Bridges components within the IBM InfoSphere installation. Look for metabroker or bridge-related modules, services, or configuration files.
    Affected if MetaBrokers & Bridges are installed, as all versions of this component are affected.

A system is affected if IBM InfoSphere Information Server version 8.1, 8.5, 8.5.0.1, 8.5.0.2, 8.7, or 9.1 is installed, or if any version of MetaBrokers & Bridges component is present, and the Import Export Manager is accessible to authenticated users.

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 IBM InfoSphere Information Server fixes: upgrade to 8.5 FP3 or later, or apply the relevant interim fix/APAR for affected versions. Implement strict input validation on the Import Export Manager component.

Fix this in Infosphere Information Server 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-2012-0705 — 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-2012-0705 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