CVE-2024-50358
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-15 "External Control of System or Configuration Setting" 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 can be exploited by authenticated users by restoring a tampered configuration backup.
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 EKI-6333AC wireless access point devices (models 2G, 2GD, and 1GPO) suffer from a CWE-15 vulnerability where authenticated users can restore a tampered configuration backup, allowing external control of system or configuration settings. The restore function lacks proper validation of configuration integrity, enabling manipulation of device settings through crafted backup files.
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.2.2< 1.6.5< 1.6.5CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify the EKI-6333AC model variantLog into the device web interface or check the device label to determine if the model is 1GPO, 2GD, or 2GAffected if The model is 1GPO, 2GD, or 2G and the firmware version falls below the fixed version for that model
-
Check the installed firmware versionAccess the device administrative interface and navigate to Status or System Information to view the current firmware version. Alternatively, use the command line and run 'cat /proc/version' or check the web interface firmware upgrade page.Affected if The firmware version is below 1.2.2 for 1GPO model, or below 1.6.5 for 2GD or 2G models
-
Verify if the configuration restore function existsNavigate to the device administrative interface and locate the Configuration Backup/Restore or Settings Restore functionality. This is typically found under System, Maintenance, or Administration menus.Affected if The device has a configuration restore or backup restore feature that accepts uploaded configuration files
-
Test if the restore function accepts modified backup filesIf you have administrative access, attempt to restore a deliberately modified configuration backup file (in a safe, isolated test environment first). Observe if the device accepts and applies the modified configuration without integrity validation errors.Affected if The device accepts and applies a tampered configuration backup without validating its integrity, indicating the vulnerability is present
The device is affected if it is an Advantech EKI-6333AC model (1GPO, 2GD, or 2G) running firmware below the respective fixed versions (1.2.2 for 1GPO, 1.6.5 for 2GD/2G) AND the configuration restore feature accepts tampered backup files without integrity validation.
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.
dbcve · scoped1.2.21.6.5
Update to vendor-patched firmware versions when available. Until then, restrict administrative access to trusted personnel only and avoid restoring configuration backups from untrusted sources.
EKI-6333AC-1GPO: firmware >= 1.2.2 | EKI-6333AC-2G and EKI-6333AC-2GD: firmware >= 1.6.5
- 1. Identify the exact model number of the Advantech EKI-6333AC device (1GPO, 2G, or 2GD).
- 2. Determine the current firmware version by accessing the device's web interface or using the CLI.
- 3. Download the appropriate firmware version from the official Advantech support website: for EKI-6333AC-1GPO use version 1.2.2 or later; for EKI-6333AC-2G and EKI-6333AC-2GD use version 1.6.5 or later.
- 4. Back up the current device configuration before performing the firmware upgrade.
- 5. Upload and install the new firmware through the device's web interface or CLI following Advantech's standard firmware update procedure.
- 6. After upgrade, verify the firmware version has been successfully updated.
- 7. Restore the configuration backup and ensure the device operates normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50358 — 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-50358 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