JTEKT TOYOPUC-PC10 ICMP denial of service

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.
4.2$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in JTEKT TOYOPUC-PC10, TOYOPUC-Plus, TOYOPUC-PC2J, TOYOPUC-PC3J and TOYOPUC-Nano. Affected is an unknown function of the component ICMP Handler. Performing a manipulation results in denial of service. This vulnerability is known as CVE-2021-33011. Access to the local network is required for this attack. No exploit is available.

Detailsinfo

A vulnerability was found in JTEKT TOYOPUC-PC10, TOYOPUC-Plus, TOYOPUC-PC2J, TOYOPUC-PC3J and TOYOPUC-Nano. It has been classified as problematic. This affects an unknown code of the component ICMP Handler. 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 weakness was published 09/10/2021 as icsa-21-245-02. The advisory is shared at us-cert.cisa.gov. This vulnerability is uniquely identified as CVE-2021-33011 since 05/13/2021. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.2

VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/13/2021 🔍
09/10/2021 +120 days 🔍
09/10/2021 +0 days 🔍
09/16/2021 +6 days 🔍

Sourcesinfo

Advisory: icsa-21-245-02
Status: Not defined

CVE: CVE-2021-33011 (🔍)
GCVE (CVE): GCVE-0-2021-33011
GCVE (VulDB): GCVE-100-182445

Entryinfo

Created: 09/10/2021 17:08
Updated: 09/16/2021 06:43
Changes: 09/10/2021 17:08 (37), 09/16/2021 06:43 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!