ORing IAP-420 up to 2.01e improper check or handling of exceptional conditions

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

Summaryinfo

A vulnerability, which was classified as problematic, was found in ORing IAP-420 up to 2.01e. Affected by this vulnerability is an unknown functionality. The manipulation results in improper check or handling of exceptional conditions. This vulnerability is reported as CVE-2024-55548. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, was found in ORing IAP-420 up to 2.01e. Affected is some unknown functionality. The manipulation with an unknown input leads to a improper check or handling of exceptional conditions vulnerability. CWE is classifying the issue as CWE-703. The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product. This is going to have an impact on availability. CVE summarizes:

Improper check of password character lenght in ORing IAP-420 allows a forced deadlock. This issue affects IAP-420: through 2.01e.

The weakness was disclosed by P. Chistè. The advisory is available at cyberdanube.com. This vulnerability is traded as CVE-2024-55548 since 12/07/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. Additional levels of successful authentication are required for exploitation. The technical details are unknown and an exploit is not 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 best quality of vulnerability data, you may have to visit VulDB.

Productinfo

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: 5.1
VulDB Meta Temp Score: 5.1

VulDB Base Score: 2.7
VulDB Temp Score: 2.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Improper check or handling of exceptional conditions
CWE: CWE-703
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

12/07/2024 🔍
12/10/2024 +3 days 🔍
12/10/2024 +0 days 🔍
10/31/2025 +325 days 🔍

Sourcesinfo

Advisory: cyberdanube.com
Researcher: P. Chistè
Status: Not defined

CVE: CVE-2024-55548 (🔍)
GCVE (CVE): GCVE-0-2024-55548
GCVE (VulDB): GCVE-100-287562

Entryinfo

Created: 12/10/2024 18:11
Updated: 10/31/2025 19:52
Changes: 12/10/2024 18:11 (64), 10/31/2025 19:52 (12)
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!