CVE-2024-39373
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 · uneditedTELSAT marKoni FM Transmitters are vulnerable to a command injection vulnerability through the manipulation of settings and could allow an attacker to gain unauthorized access to the system with administrative 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 confidenceThe TELSAT marKoni FM Transmitter suffers from a command injection vulnerability in its settings management interface. Attackers can inject arbitrary OS commands through manipulated settings parameters, which are then executed with administrative privileges, allowing complete system compromise.
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< 2.0.1< 2.0.1CVSS 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.
-
Check the firmware versionAccess the device's web-based administration interface and navigate to the Status or System Information page to view the installed firmware version. Alternatively, connect via CLI (SSH/Telnet) and run the equivalent version command if available.Affected if The displayed firmware version is lower than 2.0.1 for Markoni D (compact) or Markoni Dh (exciter+amplifiers) models.
-
Verify settings management interface availabilityConfirm the device's web-based settings management interface is accessible by attempting to log in to the administrative panel (typically on port 80 or 443). Check if the interface exposes configuration parameters for transmitter settings.Affected if The settings management interface is accessible and allows modification of transmitter parameters.
-
Identify network exposure of administrative interfaceDetermine if the administrative web interface is exposed to untrusted networks by reviewing network configuration, firewall rules, or by scanning the device's listening ports.Affected if The settings management interface is reachable from networks other than trusted management networks.
-
Review user access to settings parametersCheck which user accounts have access to the settings management functionality and whether low-privilege or guest accounts can modify settings parameters.Affected if Any user account with access to modify settings parameters exists on the system.
The device is affected if it runs firmware version below 2.0.1 AND has its settings management interface accessible to users who can modify transmitter parameters.
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 · scoped2.0.1
Implement strict input validation and sanitization on all settings parameters, avoiding direct use of user input in system calls. If system commands are required, use parameterized approaches or whitelisted input patterns.
Firmware 2.0.1 or later for Markoni D and Markoni Dh models
- Contact TELSAT to obtain the official Firmware 2.0.1 or later for your specific Markoni model (D or Dh)
- Verify the firmware integrity using checksums provided by the vendor
- Review the vendor's firmware upgrade documentation for any specific procedures
- Perform the firmware upgrade according to the vendor's instructions
- After upgrade, verify the system is functioning correctly and the vulnerability is resolved
- Consider changing administrative credentials as a precautionary measure given the vulnerability allows privilege escalation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39373 — 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-39373 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