Milesight IP Security Camera up to 2016-11-14 Web Application username/password buffer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Milesight IP Security Camera up to 2016-11-14. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component Web Application. Performing a manipulation of the argument username/password results in buffer overflow. This vulnerability is reported as CVE-2016-2356. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Milesight IP Security Camera up to 2016-11-14. It has been classified as critical. This affects an unknown code block of the component Web Application. The manipulation of the argument username/password with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Milesight IP security cameras through 2016-11-14 have a buffer overflow in a web application via a long username or password.
The weakness was disclosed 10/25/2019. This vulnerability is uniquely identified as CVE-2016-2356 since 02/12/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-144181, VDB-144180, VDB-144179 and VDB-144178 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/12/2016 🔍10/25/2019 🔍
10/26/2019 🔍
01/27/2024 🔍
Sources
Advisory: kirils.orgStatus: Not defined
CVE: CVE-2016-2356 (🔍)
GCVE (CVE): GCVE-0-2016-2356
GCVE (VulDB): GCVE-100-144177
See also: 🔍
Entry
Created: 10/26/2019 11:54Updated: 01/27/2024 13:45
Changes: 10/26/2019 11:54 (37), 10/26/2019 11:59 (17), 01/27/2024 13:45 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.