Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

fstec логотип

BDU:2017-01094

Опубликовано: 06 апр. 2017
Источник: fstec
CVSS2: 4.3
EPSS Низкий

Описание

Уязвимость операционной системы Android связана с тем, что когда безопасное приложение Qualcomm Secure Execution Environment получает адрес ячейки памяти, то он не проходит проверку на принадлежность пользовательскому пространству памяти, а не пространству памяти ядра операционной системы. Эксплуатация уязвимости может позволить нарушителю, действующему удалённо, получить расширенные привилегии

Вендор

Google Inc

Наименование ПО

Android

Версия ПО

до 7.1.1 включительно (Android)
до 7.1.1 включительно (Android)
до 7.1.1 включительно (Android)

Тип ПО

Операционная система

Операционные системы и аппаратные платформы

-

Уровень опасности уязвимости

Средний уровень опасности (базовая оценка CVSS 2.0 составляет 4,3)

Возможные меры по устранению уязвимости

Использование рекомендаций: http://www.securityfocus.com/bid/97364
https://source.android.com/security/bulletin/2017-04-01
https://www.codeaurora.org/insufficient-memory-address-information-prevent-arbitrary-memory-access-qsee-secure-applications-cve
https://www.qualcomm.com/company/product-security/security-advisories

Статус уязвимости

Подтверждена производителем

Наличие эксплойта

Данные уточняются

Информация об устранении

Уязвимость устранена

Идентификаторы других систем описаний уязвимостей

EPSS

Процентиль: 32%
0.00123
Низкий

4.3 Medium

CVSS2

Связанные уязвимости

CVSS3: 5.5
ubuntu
почти 9 лет назад

The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Secure Execution Environment (QSEE) only write to legitimate memory ranges related to the QSEE secure application's HLOS client. When secure applications inside Qualcomm Secure Execution Environment (QSEE) receive memory addresses from a high level operating system (HLOS) such as Linux Android, those address have previously been verified as belonging to HLOS memory space rather than QSEE memory space, but they were not verified to be from HLOS user space rather than kernel space. This lack of verification could lead to privilege escalation within the HLOS.

CVSS3: 5.5
nvd
почти 9 лет назад

The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Secure Execution Environment (QSEE) only write to legitimate memory ranges related to the QSEE secure application's HLOS client. When secure applications inside Qualcomm Secure Execution Environment (QSEE) receive memory addresses from a high level operating system (HLOS) such as Linux Android, those address have previously been verified as belonging to HLOS memory space rather than QSEE memory space, but they were not verified to be from HLOS user space rather than kernel space. This lack of verification could lead to privilege escalation within the HLOS.

CVSS3: 5.5
github
больше 3 лет назад

The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Secure Execution Environment (QSEE) only write to legitimate memory ranges related to the QSEE secure application's HLOS client. When secure applications inside Qualcomm Secure Execution Environment (QSEE) receive memory addresses from a high level operating system (HLOS) such as Linux Android, those address have previously been verified as belonging to HLOS memory space rather than QSEE memory space, but they were not verified to be from HLOS user space rather than kernel space. This lack of verification could lead to privilege escalation within the HLOS.

EPSS

Процентиль: 32%
0.00123
Низкий

4.3 Medium

CVSS2