CVE-2024-39148
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 · uneditedThe service wmp-agent of KerOS prior 5.12 does not properly validate so-called ‘magic URLs’ allowing an unauthenticated remote attacker to execute arbitrary OS commands as root when the service is reachable over network. Typically, the service is protected via local firewall.
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 confidenceThe wmp-agent service in KerOS versions prior to 5.12 fails to properly validate so-called 'magic URLs', allowing an unauthenticated remote attacker to bypass authentication and execute arbitrary OS commands as root. This is a critical command injection/authorization bypass vulnerability in a network-exposed service.
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>= 5.0, < 5.12CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Identify Kerlink device and Keros versionAccess the device via SSH or console and run: cat /etc/os-release or look for keros-specific version file. Alternatively, check the web management interface for firmware version information.Affected if The device is a Kerlink product running KerOS version 5.0 through 5.11 (any version < 5.12)
-
Locate the wmp-agent serviceCheck if the wmp-agent service exists on the system by running: systemctl list-units | grep wmp-agent or ps aux | grep wmp-agentAffected if The wmp-agent service is present and running on the device
-
Determine wmp-agent network exposureCheck which ports the wmp-agent service is listening on: netstat -tlnp | grep wmp-agent or ss -tlnp | grep wmp-agent. Also check firewall rules: iptables -L -n or firewall-cmd --list-allAffected if The wmp-agent service is bound to a network interface accessible from untrusted networks (0.0.0.0 or externally reachable IP)
-
Verify magic URL configuration if accessibleIf you have access to the wmp-agent configuration files, examine /etc/kerlink/wmp-agent.cfg or similar paths for any magic URL entries that could be exploited.Affected if Magic URL functionality is enabled in the wmp-agent configuration
A defender is affected if they are running any Kerlink Keros version prior to 5.12 with the wmp-agent service exposed to network 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.
dbcve · scoped5.12
Upgrade to KerOS 5.12 or later to obtain the patched wmp-agent service. Additionally, ensure the service remains protected by a local firewall and is not directly exposed to untrusted networks, as defense-in-depth.
Keros 5.12 or later
- Verify current Keros version by checking the device management interface or running 'keros-version' command
- Download Keros version 5.12 or later from the official Kerlink support portal (keros.docs.kerlink.com)
- Review upgrade documentation for device-specific procedures
- Perform firmware upgrade following Kerlink's standard upgrade process
- Verify successful upgrade by checking the new version number
- Confirm the wmp-agent service is running properly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.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,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39148 — 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-39148 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