SV3C L-SERIES HD CAMERA V2.3.4.2103-S50-NTD-B20170508B Web Interface Technical information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SV3C L-SERIES HD CAMERA V2.3.4.2103-S50-NTD-B20170508B. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Web Interface. This manipulation causes information disclosure (Technical). This vulnerability is tracked as CVE-2018-12673. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability has been found in SV3C L-SERIES HD CAMERA V2.3.4.2103-S50-NTD-B20170508B (Network Camera Software) and classified as problematic. Affected by this vulnerability is an unknown function of the component Web Interface. The manipulation with an unknown input leads to a information disclosure vulnerability (Technical). The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
An attacker with remote access to the SV3C HD Camera (L-SERIES V2.3.4.2103-S50-NTD-B20170508B and V2.3.4.2103-S50-NTD-B20170823B) web interface can disclose information about the camera including camera hardware, wireless network, and local area network information.
The bug was discovered 10/16/2018. The weakness was disclosed 10/19/2018 (Website). The advisory is shared at bishopfox.com. This vulnerability is known as CVE-2018-12673 since 06/22/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 3 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 entries VDB-125790, VDB-125793, VDB-125791 and VDB-125792 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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
Name: TechnicalClass: Information disclosure / Technical
CWE: CWE-200 / CWE-284 / CWE-266
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
06/22/2018 🔍10/16/2018 🔍
10/19/2018 🔍
10/19/2018 🔍
10/20/2018 🔍
04/05/2020 🔍
Sources
Advisory: bishopfox.comStatus: Not defined
CVE: CVE-2018-12673 (🔍)
GCVE (CVE): GCVE-0-2018-12673
GCVE (VulDB): GCVE-100-125797
See also: 🔍
Entry
Created: 10/20/2018 07:48Updated: 04/05/2020 16:46
Changes: 10/20/2018 07:48 (60), 04/05/2020 16:46 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.