CVE-2024-39208: luci-app-lucky · n/a
Affects luci-app-luckySource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubyanggao017/luci-app-luckypkg:github/yanggao017/luci-app-luckyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately identify all devices running luci-app-lucky v2.8.3 within the network through asset inventory and network scanning. 2. Restrict network access to affected devices by implementing strict firewall rules, limiting management interfaces to trusted IP addresses only. 3. Disable or remove luci-app-lucky if it is not essential for device operation or management. 4. Monitor network traffic and device logs for any unauthorized access attempts or suspicious activity targeting management interfaces. 5. Where possible, replace hardcoded credentials by modifying device firmware or configuration, though this may require vendor support or custom firmware builds. 6. Stay alert for official patches or updates from the vendor and apply them immediately upon release. 7. Employ network segmentation to isolate vulnerable devices from critical infrastructure and sensitive data. 8. Educate IT and security teams about this vulnerability to ensure rapid response and containment. 9. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect exploitation attempts targeting luci-app-lucky. 10. Engage with vendors or community support channels for potential workarounds or mitigations until official patches are available.
Description
luci-app-lucky v2.8.3 was discovered to contain hardcoded credentials.