Treck TCP-IP Stack prior 6.0.1.66 IPv6OverIPv4 Tunneling out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in Treck TCP-IP Stack. This issue affects some unknown processing of the component IPv6OverIPv4 Tunneling. Such manipulation leads to out-of-bounds. This vulnerability is uniquely identified as CVE-2020-11902. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Treck TCP-IP Stack. It has been rated as critical. Affected by this issue is an unknown function of the component IPv6OverIPv4 Tunneling. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. CVE summarizes:

The Treck TCP/IP stack before 6.0.1.66 has an IPv6OverIPv4 tunneling Out-of-bounds Read.

The weakness was disclosed 06/17/2020 as cisco-sa-treck-ip-stack-JyBQ5G as confirmed advisory (Website). The advisory is available at tools.cisco.com. This vulnerability is handled as CVE-2020-11902 since 04/19/2020. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.

Upgrading to version 6.0.1.66 eliminates this vulnerability.

The entries VDB-156836, VDB-156837, VDB-156838 and VDB-156839 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.1

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.3
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: TCP-IP Stack 6.0.1.66

Timelineinfo

04/19/2020 🔍
06/17/2020 +59 days 🔍
06/18/2020 +1 days 🔍
10/24/2020 +128 days 🔍

Sourcesinfo

Advisory: cisco-sa-treck-ip-stack-JyBQ5G
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2020-11902 (🔍)
GCVE (CVE): GCVE-0-2020-11902
GCVE (VulDB): GCVE-100-156842
See also: 🔍

Entryinfo

Created: 06/18/2020 08:18
Updated: 10/24/2020 21:15
Changes: 06/18/2020 08:18 (41), 06/18/2020 08:23 (17), 10/24/2020 21:15 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!