CVE-2020-24219 in the critical feed json
An issue was discovered on URayTech IPTV/H.264/H.265 video encoders through 1.97.
published 2020-10-06 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-16954
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 23.6%
- EPSS 23.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
An issue was discovered on URayTech IPTV/H.264/H.265 video encoders through 1.97. Attackers can send crafted unauthenticated HTTP requests to exploit path traversal and pattern-matching programming flaws, and retrieve any file from the device's file system, including the configuration file with the cleartext administrative password.
Timeline
- Published
- First public exploit (EDB-48899)
Exploit prediction
23.64% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-48899 HiSilicon Video Encoders - Unauthenticated file disclosure via path traversal webapps, 2020-10-19
- kojenov.com https://kojenov.com/2020-09-15-hisilicon-encoder-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/159595/HiSilicon-Video-Encoder-1.97-File-Disclosure-Path-Traversal.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:C/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
kojenov.com
/2020-09-15-hisilicon-encoder-vulnerabilities/
exploit, third-party-advisory
-
packetstormsecurity.com
/files/159595/HiSilicon-Video-Encoder-1.97-File-Disclosure-Path-Traversal.html
exploit, third-party-advisory, vdb-entry
-
kb.cert.org
/vuls/id/896979
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2020-24219
- NVD CVE-2020-24219
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.