Openeuler Huawei Openeuler

Do you want an email whenever new security vulnerabilities are reported in Huawei Openeuler?

By the Year

In 2022 there have been 5 vulnerabilities in Huawei Openeuler with an average score of 7.8 out of ten. Openeuler did not have any published security vulnerabilities last year. That is, 5 more vulnerabilities have already been reported in 2022 as compared to last year.

Year Vulnerabilities Average Score
2022 5 7.80
2021 0 0.00
2020 0 0.00
2019 0 0.00
2018 0 0.00

It may take a day or so for new Openeuler vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Huawei Openeuler Security Vulnerabilities

The th_read() function doesnt free a variable t->th_buf.gnu_longname after allocating memory

CVE-2021-33646 7.5 - High - August 10, 2022

The th_read() function doesnt free a variable t->th_buf.gnu_longname after allocating memory, which may cause a memory leak.

Memory Leak

The th_read() function doesnt free a variable t->th_buf.gnu_longlink after allocating memory

CVE-2021-33645 7.5 - High - August 10, 2022

The th_read() function doesnt free a variable t->th_buf.gnu_longlink after allocating memory, which may cause a memory leak.

Memory Leak

An attacker who submits a crafted tar file with size in header struct being 0 may be able to trigger an calling of malloc(0) for a variable gnu_longname

CVE-2021-33644 8.1 - High - August 10, 2022

An attacker who submits a crafted tar file with size in header struct being 0 may be able to trigger an calling of malloc(0) for a variable gnu_longname, causing an out-of-bounds read.

Out-of-bounds Read

An attacker who submits a crafted tar file with size in header struct being 0 may be able to trigger an calling of malloc(0) for a variable gnu_longlink

CVE-2021-33643 9.1 - Critical - August 10, 2022

An attacker who submits a crafted tar file with size in header struct being 0 may be able to trigger an calling of malloc(0) for a variable gnu_longlink, causing an out-of-bounds read.

Out-of-bounds Read

When setting font with malicous data by ioctl cmd PIO_FONT

CVE-2021-33656 6.8 - Medium - July 18, 2022

When setting font with malicous data by ioctl cmd PIO_FONT,kernel will write memory out of bounds.

Memory Corruption

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Debian Linux or by Huawei? Click the Watch button to subscribe.

Huawei
Vendor

subscribe