Shenzhen Sricctv DeviceViewer for XP Login Form Username memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Shenzhen Sricctv DeviceViewer for XP. Affected is an unknown function of the component Login Form. This manipulation of the argument Username causes memory corruption. This vulnerability is handled as CVE-2019-11563. The attack can be initiated remotely. Additionally, an exploit exists.
Details
A vulnerability classified as critical was found in Shenzhen Sricctv DeviceViewer for XP (the affected version is unknown). Affected by this vulnerability is an unknown code of the component Login Form. The manipulation of the argument username with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Shenzhen Sricctv DeviceViewer for XP has a Buffer Overflow via the username field on the initial login form.
The bug was discovered 04/25/2019. The weakness was released 05/09/2019 as EDB-ID 46779 as not defined exploit (Exploit-DB). It is possible to read the advisory at exploit-db.com. This vulnerability is known as CVE-2019-11563 since 04/26/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
After immediately, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 14 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (46779). Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
04/25/2019 🔍04/26/2019 🔍
05/09/2019 🔍
05/09/2019 🔍
05/09/2019 🔍
05/10/2019 🔍
10/15/2025 🔍
Sources
Advisory: EDB-ID 46779Status: Not defined
CVE: CVE-2019-11563 (🔍)
GCVE (CVE): GCVE-0-2019-11563
GCVE (VulDB): GCVE-100-134551
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/10/2019 06:52Updated: 10/15/2025 22:04
Changes: 05/10/2019 06:52 (48), 06/08/2020 16:54 (1), 09/15/2023 12:59 (8), 10/15/2025 22:04 (14)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.