GeoVision Digital Surveillance System 6.04 Encryption missing encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GeoVision Digital Surveillance System 6.04. It has been classified as critical. This impacts an unknown function of the component Encryption. This manipulation causes missing encryption. This vulnerability is tracked as CVE-2005-1553. Moreover, an exploit is present.
Details
A vulnerability has been found in GeoVision Digital Surveillance System 6.04 and classified as critical. Affected by this vulnerability is an unknown code block of the component Encryption. The manipulation with an unknown input leads to a missing encryption vulnerability. The CWE definition for the vulnerability is CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
GeoVision Digital Video Surveillance System 6.04, 6.1 and 7.0 uses a weak encryption scheme to encrypt passwords, which allows remote attackers to obtain the password via sniffing.
The weakness was disclosed 05/09/2005 (Website). The advisory is shared at esqo.com. This vulnerability is known as CVE-2005-1553 since 05/14/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but an exploit is available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
After even before and not, there has been an exploit disclosed. It is declared as proof-of-concept.
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 databases at X-Force (20538), OSVDB (16341†) and Secunia (SA15330†). The entry VDB-25176 is pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: Missing encryptionCWE: CWE-311 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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
05/09/2005 🔍05/09/2005 🔍
05/11/2005 🔍
05/11/2005 🔍
05/14/2005 🔍
05/14/2005 🔍
03/11/2015 🔍
07/23/2017 🔍
Sources
Advisory: esqo.comStatus: Not defined
CVE: CVE-2005-1553 (🔍)
GCVE (CVE): GCVE-0-2005-1553
GCVE (VulDB): GCVE-100-25177
X-Force: 20538
Secunia: 15330 - GeoVision Digital Video Surveillance System Authentication Bypass, Moderately Critical
OSVDB: 16341 - GeoVision Digital Video Surveillance System Authentication Credential Cleartext Transmission
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/11/2015 11:41Updated: 07/23/2017 10:46
Changes: 03/11/2015 11:41 (49), 07/23/2017 10:46 (8)
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.