CVE-2024-39374
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 an attacker exploiting a hidden admin account that can be accessed through the use of hard-coded credentials.
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 confidenceTELSAT marKoni FM transmitters contain a hard-coded credentials vulnerability where a hidden administrative account exists in the system firmware. An attacker with knowledge of these credentials can gain full administrative access to the transmitter, potentially allowing configuration changes, signal disruption, or further network 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your transmitter modelLocate the physical unit or documentation to confirm whether you have a Markoni Markoni D (compact) or Markoni Markoni Dh (exciter+amplifiers) unit.Affected if The model is either Markoni D or Markoni Dh and the firmware version is below 2.0.1
-
Check installed firmware versionAccess the transmitter management interface or check the firmware version through the system administration panel. Compare your firmware version against the 2.0.1 threshold.Affected if The installed firmware version is less than 2.0.1
-
Review user accounts for hidden administrative accountsAccess the user management or accounts configuration section of the transmitter web interface or CLI. Look for any unexpected or undocumented administrative accounts beyond those you created.Affected if A hidden or undocumented administrative account exists in the system that you did not create
-
Verify management interface exposureCheck network configuration to determine if the transmitter management interface (web UI, SSH, or telnet) is accessible from external or untrusted networks.Affected if The transmitter management interface is exposed to untrusted networks without proper network segmentation or firewall controls
-
Inspect configuration for default or static credentialsExport or review the transmitter configuration files and look for hardcoded username/password pairs, especially for administrative-level accounts.Affected if Configuration contains hardcoded or static credentials for administrative access
You are affected if you have a Markoni D or Markoni Dh transmitter running firmware version lower than 2.0.1 that contains a hidden administrative account with hardcoded credentials.
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 data2.0.1
Immediately change or disable the hidden admin account credentials, contact the vendor for firmware updates that remove hard-coded credentials, and implement network segmentation to limit exposure of the transmitter management interfaces.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39374 — 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-39374 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