| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Chicken of the VNC 2.0. The impacted element is an unknown function. Performing a manipulation results in denial of service. This vulnerability was named CVE-2007-0756. In addition, an exploit is available.
Details
A vulnerability, which was classified as critical, was found in Chicken of the VNC 2.0. This affects an unknown functionality. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
Chicken of the VNC (cotv) 2.0 allows remote attackers to cause a denial of service (application crash) via a large computer-name size value in a ServerInit packet, which triggers a failed malloc and a resulting NULL dereference.
The weakness was presented 02/02/2007 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2007-0756 since 02/05/2007. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.
A public exploit has been developed by poplix and been published even before and not after the advisory. The exploit is shared for download at securityfocus.com. 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 (32166), Exploit-DB (3257), SecurityFocus (BID 22372†) and OSVDB (33637†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.5
VulDB Temp Score: 7.1
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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: poplix
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
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: 🔍
Timeline
02/02/2007 🔍02/02/2007 🔍
02/02/2007 🔍
02/02/2007 🔍
02/05/2007 🔍
02/05/2007 🔍
02/25/2007 🔍
03/13/2015 🔍
08/21/2024 🔍
Sources
Advisory: securityfocus.com⛔Status: Confirmed
CVE: CVE-2007-0756 (🔍)
GCVE (CVE): GCVE-0-2007-0756
GCVE (VulDB): GCVE-100-34833
X-Force: 32166 - Chicken of the VNC ServerInit packets denial of service
SecurityFocus: 22372 - Chicken of the VNC Remote Denial of Service Vulnerability
OSVDB: 33637 - Chicken of the VNC ServerInit Packet computer-name Size Overflow DoS
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/13/2015 12:16Updated: 08/21/2024 13:50
Changes: 03/13/2015 12:16 (56), 10/09/2017 16:56 (5), 08/21/2024 13:50 (17)
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.