ALEOS up to 4.4.8/4.9.4/4.12.x API AT Command memory corruption

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

Summaryinfo

A vulnerability was found in ALEOS up to 4.4.8/4.9.4/4.12.x and classified as problematic. The affected element is an unknown function of the component API. The manipulation as part of AT Command results in privilege escalation. This vulnerability is reported as CVE-2019-11848. The attack can be launched remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in ALEOS up to 4.4.8/4.9.4/4.12.x. Affected is an unknown code of the component API. The manipulation as part of a AT Command leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

An API abuse vulnerability exists in the AT command API of ALEOS before 4.13.0, 4.9.5, 4.4.9 due to lack of length checking when handling certain user-provided values.

The weakness was disclosed 08/21/2020. This vulnerability is traded as CVE-2019-11848 since 05/09/2019. The exploitability is told to be difficult. 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.

Upgrading to version 4.4.9, 4.9.5 or 4.13.0 eliminates this vulnerability.

The entries VDB-160126, VDB-160125, VDB-160124 and VDB-160123 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.1
VulDB Meta Temp Score: 4.0

VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.1
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Memory corruption
CWE: 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: ALEOS 4.4.9/4.9.5/4.13.0

Timelineinfo

05/09/2019 🔍
08/21/2020 +470 days 🔍
08/22/2020 +1 days 🔍
11/10/2020 +80 days 🔍

Sourcesinfo

Status: Not defined

CVE: CVE-2019-11848 (🔍)
GCVE (CVE): GCVE-0-2019-11848
GCVE (VulDB): GCVE-100-160122
See also: 🔍

Entryinfo

Created: 08/22/2020 06:48
Updated: 11/10/2020 20:45
Changes: 08/22/2020 06:48 (37), 08/22/2020 06:53 (10), 11/10/2020 20:45 (2)
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.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!