dbcve.org
Powerstation FirmwareOperating system · Hgiga

CVE-2023-24838

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
HGiga PowerStation has a vulnerability of Information Leakage. An unauthenticated remote attacker can exploit this vulnerability to obtain the administrator's credential. This credential can then be used to login PowerStation or Secure Shell to achieve remote code execution.

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

HGiga PowerStation contains an information leakage vulnerability allowing unauthenticated remote attackers to obtain administrator credentials. The leaked credentials can then be used to authenticate to the PowerStation administrative interface or via SSH, enabling remote code execution.

MitigationApply vendor-supplied security patches immediately. As an interim measure, restrict network access to the PowerStation admin interface and SSH services to trusted IP addresses only.

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
Powerstation FirmwareOperating system
Affected:< x64.6.2.165

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 device as HGiga PowerStation
    Access the administrative web interface or check system documentation to confirm the product is HGiga PowerStation. Look for PowerStation branding or check the device model information in the admin panel.
    Affected if The device is confirmed to be HGiga PowerStation firmware.
  2. Determine the firmware version
    In the PowerStation admin interface, navigate to System Settings or Status/About page to view the installed firmware version. Alternatively, access the device via SSH and run: cat /etc/version or ls -la /firmware/ to identify the version number.
    Affected if The installed firmware version is lower than x64.6.2.165 (e.g., x64.6.2.100, x64.6.1.x, etc.).
  3. Verify admin interface accessibility
    Attempt to access the PowerStation web admin interface from an untrusted network location. Check firewall rules or network configuration to confirm whether port 443, 80, or the admin web port is exposed to the internet or untrusted networks.
    Affected if The admin web interface is accessible from untrusted/external IP addresses without IP restriction.
  4. Check SSH service exposure
    Verify if SSH (port 22) is listening and accessible from untrusted networks. Use nmap or telnet to test connectivity: nmap -p 22 <device-ip> or check firewall rules for inbound SSH access.
    Affected if SSH service is accessible from untrusted/external IP addresses without IP restriction.

You are affected if the device is HGiga PowerStation with firmware version lower than x64.6.2.165 AND the admin interface or SSH service is accessible from untrusted networks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied security patches immediately. As an interim measure, restrict network access to the PowerStation admin interface and SSH services to trusted IP addresses only.

Recommended fix Moderate confidence

x64.6.2.165 or later

  1. 1. Download the latest PowerStation firmware version x64.6.2.165 or later from the official HGiga vendor website.
  2. 2. Access the PowerStation administrative interface or console.
  3. 3. Navigate to the firmware update or system maintenance section.
  4. 4. Upload the downloaded firmware file and initiate the upgrade process.
  5. 5. Verify the firmware version after upgrade to confirm x64.6.2.165 or later is installed.
  6. 6. Change the administrator password immediately after upgrade, as the vulnerability may have exposed the original credential.
  7. 7. Review system logs for any unauthorized access attempts prior to the patch.

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

Fix this in Powerstation Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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