Westermo L210-F2G Lynx 4.21.0 improper control of interaction frequency

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

Summaryinfo

A vulnerability classified as critical has been found in Westermo L210-F2G Lynx 4.21.0. This vulnerability affects unknown code. The manipulation leads to improper control of interaction frequency. This vulnerability is documented as CVE-2024-32943. The attack can be initiated remotely. There is not any exploit available. Disabling the affected component is recommended.

Detailsinfo

A vulnerability was found in Westermo L210-F2G Lynx 4.21.0. It has been rated as critical. This issue affects some unknown processing. The manipulation with an unknown input leads to a improper control of interaction frequency vulnerability. Using CWE to declare the problem leads to CWE-799. The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests. Impacted is availability. The summary by CVE is:

An attacker may be able to cause a denial-of-service condition by sending many SSH packets repeatedly.

The advisory is shared at cisa.gov. The identification of this vulnerability is CVE-2024-32943. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

The best possible mitigation is suggested to be disabling the affected component.

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

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.4

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

CNA Base Score: 7.5
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Improper control of interaction frequency
CWE: CWE-799 / CWE-400 / CWE-404
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: Disable
Status: 🔍

0-Day Time: 🔍

Timelineinfo

06/20/2024 🔍
06/20/2024 +0 days 🔍
07/30/2025 +405 days 🔍

Sourcesinfo

Advisory: icsa-24-172-03
Status: Confirmed

CVE: CVE-2024-32943 (🔍)
GCVE (CVE): GCVE-0-2024-32943
GCVE (VulDB): GCVE-100-269261

Entryinfo

Created: 06/20/2024 17:48
Updated: 07/30/2025 20:32
Changes: 06/20/2024 17:48 (51), 07/30/2025 20:32 (25)
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!