CVE-2024-28747
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 · uneditedAn unauthenticated remote attacker can use the hard-coded credentials to access the SmartSPS devices with high privileges.
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 confidenceHard-coded credentials embedded in SmartSPS device firmware allow an unauthenticated remote attacker to bypass authentication and gain high-privilege access to the device without any credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is a SmartSPS modelIdentify the device by checking its model number, branding, or administrative interface for 'SmartSPS' designation. This can be done via device label, web UI, or SNMP enumeration.Affected if The device is a SmartSPS product from any affected vendor
-
Check if remote network access is enabledReview device network configuration settings (web interface, SSH, telnet, or management protocol settings) to determine if remote administrative access is permitted from untrusted networks.Affected if Remote access is enabled and the device is reachable from untrusted networks
-
Inspect firmware for embedded credentialsExtract firmware image (via manufacturer download, TFTP dump, or flash memory read) and analyze binary or filesystem for hardcoded strings matching patterns like usernames, passwords, or API keys that are not user-configurable.Affected if Hardcoded credentials exist in the firmware that were not set by the administrator
-
Verify no custom credentials override default accountsCheck device user account settings to confirm all accounts with administrative privileges were created or changed by administrators, and that no factory-default high-privilege accounts remain active.Affected if Default factory accounts with high privileges are still active and cannot be traced to administrator creation
-
Compare installed firmware version against vendor release notesRetrieve firmware version from device (web UI status page, CLI 'show version', or SNMP OID) and compare to any vendor advisories or release notes addressing credential vulnerabilities.Affected if Firmware version predates the credential removal patch or version cannot be determined
The environment is affected if a SmartSPS device has remote network access enabled and contains hardcoded credentials that provide unauthenticated high-privilege access.
Generated from the published advisory. Verify against your own configuration.
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 dataImmediately restrict network exposure of SmartSPS devices, change any default credentials, contact vendor for firmware update to remove hard-coded credentials, and implement proper credential management.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28747 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28747 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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