dbcve.org
Datapower GatewayApplication · Ibm

CVE-2019-4621

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-09
Fix available
A fix is available. Upgrade to after 2018.4.1.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
IBM DataPower Gateway 7.6.0.0-7 throug 6.0.14 and 2018.4.1.0 through 2018.4.1.5 have a default administrator account that is enabled if the IPMI LAN channel is enabled. A remote attacker could use this account to gain unauthorised access to the BMC. IBM X-Force ID: 168883.

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

IBM DataPower Gateway versions 7.6.0.0-7 through 6.0.14 and 2018.4.1.0 through 2018.4.1.5 contain a default administrator account that becomes enabled when the IPMI LAN channel is configured. This default credential allows remote attackers to authenticate to the Baseboard Management Controller (BMC) with full administrative privileges.

MitigationDisable the IPMI LAN channel in the BMC configuration or change the default administrator password to prevent exploitation of this default credential vulnerability.

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
Datapower GatewayApplication
Affected:>= 7.6.0.0, <= 7.6.0.14>= 2018.4.1.0, <= 2018.4.1.5

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installed IBM DataPower Gateway version
    Run 'show version' or access the administrative console to view the firmware version
    Affected if Version is 7.6.0.0 through 7.6.0.14, or 2018.4.1.0 through 2018.4.1.5
  2. Check IPMI LAN channel configuration
    Access the Baseboard Management Controller (BMC) configuration interface and locate the IPMI LAN channel settings
    Affected if IPMI LAN channel is enabled or configured on the system
  3. Verify default administrator account status
    Examine BMC user accounts list to confirm if the default administrator account (typically 'ADMIN' or 'root') is active
    Affected if Default administrator account exists and is enabled in BMC user configuration
  4. Confirm remote IPMI access is permitted
    Check BMC network settings to determine if IPMI over LAN access is allowed from non-local networks
    Affected if IPMI LAN access is permitted from network interfaces accessible to attackers

You are affected if your IBM DataPower Gateway version falls within the vulnerable ranges AND the IPMI LAN channel is configured, enabling the default BMC administrator credential.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2018.4.1.5
Interim mitigation

Disable the IPMI LAN channel in the BMC configuration or change the default administrator password to prevent exploitation of this default credential vulnerability.

Recommended fix Moderate confidence

DataPower Gateway 7.6.0.15 or later; 2018.4.1.6 or later

  1. Disable the IPMI LAN channel if not required, through the DataPower web interface or CLI
  2. If IPMI is required, ensure the default administrator account credentials are changed immediately upon initial setup
  3. Upgrade DataPower Gateway 7.6.0.0-7.6.0.14 to version 7.6.0.15 or later
  4. Upgrade DataPower Gateway 2018.4.1.0-2018.4.1.5 to version 2018.4.1.6 or later
  5. After upgrade, verify IPMI configuration and ensure default credentials have been changed
  6. Restrict IPMI/BMC network access to trusted management networks only
Caveat Standard IBM DataPower maintenance upgrade; review IBM release notes for any compatibility concerns with custom configurations or integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Datapower Gateway Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2019-4621 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