dbcve.org
Ap9630 FirmwareOperating system · Schneider Electric

CVE-2018-7820

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-17
Fix available
A fix is available. Upgrade to 6.7.2 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
A Credentials Management CWE-255 vulnerability exists in the APC UPS Network Management Card 2 AOS v6.5.6, which could cause Remote Monitoring Credentials to be viewed in plaintext when Remote Monitoring is enabled, and then disabled.

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

The APC UPS Network Management Card 2 AOS v6.5.6 has a CWE-255 credentials management vulnerability where Remote Monitoring credentials are stored in plaintext and remain visible even after Remote Monitoring is disabled. When a user enables then disables the Remote Monitoring feature, the credentials are not properly cleared from memory/storage, allowing unauthorized disclosure of sensitive authentication credentials.

MitigationApply the vendor-supplied firmware patch for AOS v6.5.6 to remediate the plaintext credential storage issue. As a compensating control, ensure Remote Monitoring is only enabled when actively needed and consider rotating credentials after any instance of enabling/disabling this feature.

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
Ap9630 FirmwareOperating system
Affected:< 6.7.2
Smart Ups Srt 5kva FirmwareOperating system
Affected:< 6.7.2
Ap9631 FirmwareOperating system
Affected:< 6.7.2
Ap9635 FirmwareOperating system
Affected:< 6.7.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
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 the firmware version
    Access the APC Network Management Card web interface and navigate to the About/Firmware Information page, or query via SNMP (snmpget on OID .1.3.6.1.4.1.318.1.1.1.1.1.1.0). Compare the displayed firmware version to 6.7.2.
    Affected if The installed firmware version is less than 6.7.2.
  2. Check if Remote Monitoring was ever enabled
    Access the Network Management Card web interface and navigate to the Remote Monitoring configuration section. Look for the current status and any history indicating the feature was previously enabled.
    Affected if Remote Monitoring was enabled at any point, regardless of current enabled/disabled state.
  3. Verify credential visibility
    In the Network Management Card web interface, go to the Remote Monitoring or Network settings and examine whether the stored credentials (username/password) are visible in plaintext after disabling the feature.
    Affected if Credentials are visible in plaintext after Remote Monitoring has been disabled.
  4. Check for credential persistence in backup/config exports
    If configuration backups are available, examine any exported configuration files or backups for plaintext credential storage. These may contain residual Remote Monitoring credentials.
    Affected if Backup or configuration files contain plaintext credentials that should have been cleared.

You are affected if your firmware version is below 6.7.2 and Remote Monitoring was ever enabled, with credentials remaining visible in plaintext after disabling the feature.

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 6.7.2 or later
Fixed in 6.7.2
Interim mitigation

Apply the vendor-supplied firmware patch for AOS v6.5.6 to remediate the plaintext credential storage issue. As a compensating control, ensure Remote Monitoring is only enabled when actively needed and consider rotating credentials after any instance of enabling/disabling this feature.

Recommended fix High confidence

Firmware version 6.7.2 or later for Ap9630, Ap9631, Ap9635, and Smart UPS SRT 5kva

  1. Download APC Network Management Card firmware version 6.7.2 or later from the official APC website (www.apc.com)
  2. Access the NMC web interface for the affected device (Ap9630, Ap9631, Ap9635, or Smart UPS SRT 5kva)
  3. Navigate to the Firmware Update or Administration section in the web UI
  4. Upload and apply the firmware version 6.7.2 or later
  5. After the device reboots, verify the new firmware version is installed
  6. Confirm that Remote Monitoring credentials are no longer exposed in plaintext after toggling the Remote Monitoring setting
Caveat Firmware upgrades on UPS devices carry inherent risk; ensure proper power backup and follow APC upgrade documentation carefully

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

Fix this in Ap9630 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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