Threats / Cisco / CVE-2024-20439
CVE-2024-20439
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Cisco Smart Licensing Utility vulnerability
Cisco Smart Licensing Utility contains a static credential vulnerability allowing unauthenticated remote attackers to gain administrative access to affected systems.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can exploit hardcoded credentials in Cisco Smart Licensing Utility to obtain administrative privileges, enabling full system compromise. High exploitation likelihood is evidenced by active wild exploitation and EPSS score of 0.87.
CISA KEV Yes · 2025-03-315EPSS 0.92062 (verify live)6CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4Exploit Public PoC / detection · nuclei template13
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
499 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-03-31).
Probability (EPSS)
EPSS 0.92062 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Cisco, Smart Licensing Utility. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-912 Hidden Functionality.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 208 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
WeaknessCWE-912 · Hidden Functionality
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I discover the static credential embedded in Cisco Smart Licensing Utility through documentation, source code analysis, or public disclosure.
Business
Attackers gain a reliable, repeatable method to compromise licensing infrastructure across customer deployments without requiring authentication.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I connect remotely to the affected Smart Licensing Utility instance and authenticate using the hardcoded credentials.
Business
Administrative access is obtained to systems managing software licensing and compliance tracking across the organization.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent administrative control over the licensing utility and pivot to connected systems or extract sensitive configuration data.
Business
Attackers can manipulate license records, disable compliance monitoring, or use the compromised system as a foothold for lateral movement within the network.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05