dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2024-28146

HIGH · 8.4 CVSS v3.1 Published 2024-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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
The application uses several hard-coded credentials to encrypt config files during backup, to decrypt the new firmware during an update and some passwords allow a direct connection to the database server of the affected device.

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

The application embeds hard-coded credentials used for encrypting configuration files during backup operations and decrypting firmware during updates. Additionally, some hard-coded passwords provide direct database server access on the affected device. These credentials are static and cannot be rotated, allowing anyone with firmware access to extract them and compromise the encryption mechanisms and database.

MitigationReplace all hard-coded credentials with a secure secrets management solution (e.g., hardware security module, encrypted keystore, or external secrets service) that supports credential rotation and secure injection at runtime. Implement proper authentication for database access and verify the firmware update chain-of-trust.

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

CVSS:3.1/AV:L/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 application and firmware version
    Locate the installed application version through the product's web interface, CLI command, or firmware file name. Common paths: /etc/version, about page, or firmware metadata file.
    Affected if The version matches or predates the release containing CVE-2024-28146 (check vendor advisory for specific version numbers)
  2. Extract and inspect the firmware binary for hard-coded strings
    If you have access to the firmware file, use binwalk or strings to extract readable text. Run 'strings firmware.bin | grep -i -E "(password|key|secret|credential)"' and examine any static-looking values.
    Affected if Hard-coded passwords, keys, or secrets are found embedded in the binary that cannot be changed through configuration
  3. Analyze backup encryption mechanism
    Create a configuration backup if the feature exists. Examine the backup file format and attempt to identify the encryption method and any embedded keys used to protect it.
    Affected if The backup file uses a static, non-rotatable key embedded in the application code
  4. Check for database access with embedded credentials
    Attempt to access the database service using common internal ports (e.g., MySQL 3306, PostgreSQL 5432, SQLite file). Test if any default or embedded credentials provide direct access without proper authentication configuration.
    Affected if The database is accessible using hard-coded credentials that are present in the firmware or application binary
  5. Inspect configuration files for static credentials
    Examine any configuration files, scripts, or initialization files included in the firmware or application installation for hard-coded passwords, encryption keys, or database credentials that should be configurable.
    Affected if Static credentials are found that cannot be rotated through the product's admin interface or are shared across all deployments

A user is affected if the application contains embedded, non-rotatable credentials used for backup encryption, firmware decryption, or database access that are present in the firmware or binary regardless of configuration.

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

Replace all hard-coded credentials with a secure secrets management solution (e.g., hardware security module, encrypted keystore, or external secrets service) that supports credential rotation and secure injection at runtime. Implement proper authentication for database access and verify the firmware update chain-of-trust.

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
76.0 hours of engineering $13,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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