CVE-2024-50377
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 · uneditedA CWE-798 "Use of Hard-coded Credentials" was discovered affecting the following devices manufactured by Advantech: EKI-6333AC-2G (<= 1.6.3), EKI-6333AC-2GD (<= v1.6.3) and EKI-6333AC-1GPO (<= v1.2.1). The vulnerability is associated to the backup configuration functionality that by default encrypts the archives using a static password.
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 confidenceAdvantech wireless access points (EKI-6333AC-2G, EKI-6333AC-2GD, EKI-6333AC-1GPO) contain hardcoded credentials in their backup configuration functionality. The backup archives are encrypted using a static password that is hardcoded into the firmware, allowing anyone who obtains this password to decrypt and extract sensitive configuration data.
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< 1.6.5< 1.6.5< 1.2.2CVSS 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
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/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.
-
Identify your exact device modelLog into the device web interface or check the physical label to confirm the model is one of EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPOAffected if The model is any of these three variants
-
Check installed firmware versionAccess the device web interface and navigate to the Status or System Information page to view the firmware version, or use the command line and run 'cat /proc/version' or 'firmwareversion' if availableAffected if Firmware version is below 1.6.5 for EKI-6333AC-2G or EKI-6333AC-2GD, or below 1.2.2 for EKI-6333AC-1GPO
-
Locate backup configuration filesCheck for .cfg or .backup files on the device via the web interface (typically under Maintenance > Backup/Restore) or via FTP/TFTP if enabledAffected if Any backup configuration archives exist on the device or have been exported
-
Inspect firmware for hardcoded password stringsIf you have access to the firmware image (download from vendor or extract from device), search for static strings related to backup encryption using binwalk, strings, or a hex editorAffected if A static encryption password is found embedded in the firmware binary
You are affected if you own an EKI-6333AC model and your firmware version falls below the thresholds (1.6.5 for 2G/2GD, 1.2.2 for 1GPO) and backup configuration files using the hardcoded password exist or the password is present in the firmware.
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 data1.2.21.6.5
Change the default encryption password in the backup configuration functionality immediately. If available, apply vendor firmware updates that remove the hardcoded credentials. Contact Advantech for patched firmware versions.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50377 — 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-50377 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