dbcve.org
Moonshot Remote Console AdministratorApplication · Hp

CVE-2017-12543

MEDIUM · 6.5 CVSS v3.0 Published 2018-02-15
Fix available
A fix is available. Upgrade to 1.89 / 2.30 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A remote disclosure of information vulnerability in Moonshot Remote Console Administrator Prior to 2.50, iLO4 prior to v2.53, iLO3 prior to v1.89 and iLO2 prior to v2.30 was found.

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

This is a remote information disclosure vulnerability in HPE iLO (Integrated Lights-Out) firmware versions and Moonshot Remote Console Administrator. An unauthenticated remote attacker could potentially access sensitive information through the management interface.

MitigationUpdate affected systems to iLO2 v2.30 or later, iLO3 v1.89 or later, iLO4 v2.53 or later, or Moonshot Remote Console Administrator v2.50 or later.

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
Moonshot Remote Console AdministratorApplication
Affected:< 2.50
Integrated Lights Out 2 FirmwareOperating system
Affected:< 2.30
Integrated Lights Out 3 FirmwareOperating system
Affected:< 1.89
Integrated Lights Out 4 FirmwareOperating system
Affected:< 2.53

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify HPE iLO firmware version via web interface
    Log into the iLO web interface (typically at https://<server-ip>/ilo or https://<server-hostname>/) and navigate to the 'Administration' or 'Information' section to view the firmware version. The version is usually displayed as 'iLO X Firmware Version' where X is 2, 3, or 4.
    Affected if The displayed firmware version is below 2.30 for iLO2, below 1.89 for iLO3, or below 2.53 for iLO4.
  2. Identify HPE iLO firmware version via command line
    Use the HPE ilorest tool (ilorest) or hponcfg utility on the host server to query the iLO firmware version. Run 'ilorest login <iLO-ip> -u <username> -p <password> && ilorest get HPEFirmwareVersion' or check the output of 'hponcfg -g' for the firmware version.
    Affected if The reported firmware version is below 2.30 for iLO2, below 1.89 for iLO3, or below 2.53 for iLO4.
  3. Check iLO firmware version via SNMP
    Query the iLO interface via SNMP using an SNMP client. The firmware version is typically available under the SNMP OID for iLO firmware. Use 'snmpwalk -v2c -c <community> <iLO-ip> .1.3.6.1.4.1.232.9.2.2' or similar HPE iLO MIB tree to retrieve the firmware version.
    Affected if The SNMP response shows a version below 2.30 for iLO2, below 1.89 for iLO3, or below 2.53 for iLO4.
  4. Identify Moonshot Remote Console Administrator version
    Check the installed version of Moonshot Remote Console Administrator on the system where it is installed. This can be done via the Windows 'Add or Remove Programs' list, the application's 'About' or 'Help' menu, or by checking the program's installation directory for version information.
    Affected if The installed version is below 2.50.
  5. Confirm iLO model before version check
    Before comparing versions, confirm whether the system uses iLO2, iLO3, or iLO4. This is typically visible in the iLO web interface header, in the system information section, or via command line tools like ilorest which report the iLO generation. Different generations have different fixed version thresholds.
    Affected if The iLO generation (2, 3, or 4) is confirmed and the corresponding version is below the threshold listed in the affected versions.

Your environment is affected if HPE iLO firmware (any generation) or Moonshot Remote Console Administrator is present and the installed version falls below the minimum fixed version for that specific product.

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
Upgrade available Upgrade to 1.89 / 2.30 / 2.50 or later
Fixed in 1.892.302.50
Interim mitigation

Update affected systems to iLO2 v2.30 or later, iLO3 v1.89 or later, iLO4 v2.53 or later, or Moonshot Remote Console Administrator v2.50 or later.

Fix this in Moonshot Remote Console Administrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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