Infosphere Replication ServerApplication · Ibm

CVE-2013-0584

MEDIUM · 5.0 CVSS v2.0 Published 2013-04-23
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
The Data Replication Dashboard component in IBM InfoSphere Replication Server 9.7 and 10.x before 10.2.0.0-b113 allows remote attackers to obtain a list of all user accounts, along with information about whether each account requires a password, 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 · moderate confidence

The Data Replication Dashboard component in IBM InfoSphere Replication Server versions 9.7 and 10.x before 10.2.0.0-b113 contains an information disclosure vulnerability allowing remote attackers to obtain a list of all user accounts along with information about whether each account requires a password, via unspecified vectors.

MitigationUpgrade to IBM InfoSphere Replication Server version 10.2.0.0-b113 or later to patch the vulnerability. Consider restricting network access to the Data Replication Dashboard until the patch can be applied.

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 Replication ServerApplication
Affected:= 9.7= 10.1.0= 10.1.0.1= 10.1.0.2= 10.1.0.3= 10.1.0.4= 10.2.0.0

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. Verify IBM InfoSphere Replication Server is installed
    Check for IBM InfoSphere Replication Server installation via system inventory, package manager, or by locating common installation directories such as $IMSPATH or /opt/IBM/information-server
    Affected if The product is present on the system
  2. Determine the installed version of IBM InfoSphere Replication Server
    Run the appropriate version command or check the installation manifest. Typical methods include using the 'dmpmaster' utility, checking the 'registry.xml' file in the installation directory, or running 'iis_version' if available
    Affected if The installed version is 9.7 (any subversion), 10.1.0.x (where x is 0-4), or 10.2.0.0 prior to fix pack b113
  3. Confirm Data Replication Dashboard component is enabled
    Check the IBM InfoSphere Replication Server configuration for the Data Replication Dashboard service status. This is typically accessible via the IBM InfoSphere Data Replication Dashboard web interface or through the Q REPLICATION (or similar) setup scripts
    Affected if The Data Replication Dashboard web component is accessible and operational on the server
  4. Assess network accessibility of the Data Replication Dashboard
    Review firewall rules, network configuration, and access controls around the Data Replication Dashboard web port (commonly port 8080, 8443, or the configured HTTP/HTTPS port for the dashboard). Check if it is exposed to untrusted networks
    Affected if The Data Replication Dashboard is reachable from networks outside the trusted administrative zone

A user is affected if IBM InfoSphere Replication Server versions 9.7 through 10.1.0.4, or version 10.2.0.0 before fix pack b113, is installed with the Data Replication Dashboard component enabled and 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 Replication Server version 10.2.0.0-b113 or later to patch the vulnerability. Consider restricting network access to the Data Replication Dashboard until the patch can be applied.

Fix this in Infosphere Replication Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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