漏洞修补列表

nginx

1.25.4

HWPSIRT-2024-61183

CVE-2024-34161

5.3

When NGINX Plus or NGINX OSS are configured to use the HTTP/3 QUIC module and the network infrastructure supports a Maximum Transmission Unit (MTU) of 4096 or greater without fragmentation, undisclosed QUIC packets can cause NGINX worker processes to leak previously freed memory.

Kunpeng DevKit 24.0.RC2

google/protobuf

3.13.0

HWPSIRT-2022-48925

CVE-2022-3171

7.5

A parsing issue with binary data in protobuf-java core and lite versions prior to 3.21.7, 3.20.3, 3.19.6 and 3.16.3 can lead to a denial of service attack. Inputs containing multiple instances of non-repeated embedded messages with repeated or unknown fields causes objects to be converted back-n-forth between mutable and immutable forms, resulting in potentially long garbage collection pauses. We recommend updating to the versions mentioned above.

Kunpeng DevKit 24.0.RC1

zlib

1.2.13

HWPSIRT-2023-88530

CVE-2023-45853

9.8

MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected zlib version, and exposes the applicable MiniZip code through its compress API.

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2022-30512

CVE-2022-42919

7.8

Python 3.9.x before 3.9.16 and 3.10.x before 3.10.9 on Linux allows local privilege escalation in a non-default configuration. The Python multiprocessing library, when used with the forkserver start method on Linux, allows pickles to be deserialized from any user in the same machine local network namespace, which in many system configurations means any user on the same machine. Pickles can execute arbitrary code. Thus, this allows for local user privilege escalation to the user that any forkserver process is running as. Setting multiprocessing.util.abstract_sockets_supported to False is a workaround. The forkserver start method for multiprocessing is not the default start method. This issue is Linux specific because only Linux supports abstract namespace sockets. CPython before 3.9 does not make use of Linux abstract namespace sockets by default. Support for users manually specifying an abstract namespace socket was added as a bugfix in 3.7.8 and 3.8.3, but users would need to make specific uncommon API calls in order to do that in CPython before 3.9.

Kunpeng DevKit 24.0.RC1

nginx

1.24.0

HWPSIRT-2023-50241

CVE-2023-44487

7.5

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2023-92374

CVE-2023-40217

5.3

An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18, 3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)

Kunpeng DevKit 24.0.RC1

OpenSSL

3.0.9

HWPSIRT-2023-38714

CVE-2023-5363

7.5

Issue summary: A bug has been identified in the processing of key and

initialisation vector (IV) lengths. This can lead to potential truncation

or overruns during the initialisation of some symmetric ciphers.

Impact summary: A truncation in the IV can result in non-uniqueness,

which could result in loss of confidentiality for some cipher modes.

When calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or

EVP_CipherInit_ex2() the provided OSSL_PARAM array is processed after

the key and IV have been established. Any alterations to the key length,

via the "keylen" parameter or the IV length, via the "ivlen" parameter,

within the OSSL_PARAM array will not take effect as intended, potentially

causing truncation or overreading of these values. The following ciphers

and cipher modes are impacted: RC2, RC4, RC5, CCM, GCM and OCB.

For the CCM, GCM and OCB cipher modes, truncation of the IV can result in

loss of confidentiality. For example, when following NIST's SP 800-38D

section 8.2.1 guidance for constructing a deterministic IV for AES in

GCM mode, truncation of the counter portion could lead to IV reuse.

Both truncations and overruns of the key and overruns of the IV will

produce incorrect results and could, in some cases, trigger a memory

exception. However, these issues are not currently assessed as security

critical.

Changing the key and/or IV lengths is not considered to be a common operation

and the vulnerable API was recently introduced. Furthermore it is likely that

application developers will have spotted this problem during testing since

decryption would fail unless both peers in the communication were similarly

vulnerable. For these reasons we expect the probability of an application being

vulnerable to this to be quite low. However if an application is vulnerable then

this issue is considered very serious. For these reasons we have assessed this

issue as Moderate severity overall.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this because

the issue lies outside of the FIPS provider boundary.

OpenSSL 3.1 and 3.0 are vulnerable to this issue.

Kunpeng DevKit 24.0.RC1

OpenSSL

3.0.9

HWPSIRT-2023-63472

CVE-2023-3446

5.3

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex()

or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long

delays. Where the key or parameters that are being checked have been obtained

from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. One of those

checks confirms that the modulus ('p' parameter) is not too large. Trying to use

a very large modulus is slow and OpenSSL will not normally use a modulus which

is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters

that have been supplied. Some of those checks use the supplied modulus value

even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained

from an untrusted source could be vulernable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions.

An application calling any of those other functions may similarly be affected.

The other functions affected by this are DH_check_ex() and

EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications

when using the '-check' option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2022-73587

CVE-2021-28861

7.4

Python 3.x through 3.10 has an open redirection vulnerability in lib/http/server.py due to no protection against multiple (/) at the beginning of URI path which may leads to information disclosure. NOTE: this is disputed by a third party because the http.server.html documentation page states "Warning: http.server is not recommended for production. It only implements basic security checks."

Kunpeng DevKit 24.0.RC1

openEuler:c-ares

1.18.1-5.oe2203sp1

HWPSIRT-2023-46789

CVE-2023-31147

6.5

c-ares is an asynchronous resolver library. When /dev/urandom or RtlGenRandom() are unavailable, c-ares uses rand() to generate random numbers used for DNS query ids. This is not a CSPRNG, and it is also not seeded by srand() so will generate predictable output. Input from the random number generator is fed into a non-compilant RC4 implementation and may not be as strong as the original RC4 implementation. No attempt is made to look for modern OS-provided CSPRNGs like arc4random() that is widely available. This issue has been fixed in version 1.19.1.

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2022-23306

CVE-2018-25032

7.5

zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.

Kunpeng DevKit 24.0.RC1

OpenSSL

3.0.9

HWPSIRT-2024-83093

CVE-2024-0727

5.5

Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL

to crash leading to a potential Denial of Service attack

Impact summary: Applications loading files in the PKCS12 format from untrusted

sources might terminate abruptly.

A file in PKCS12 format can contain certificates and keys and may come from an

untrusted source. The PKCS12 specification allows certain fields to be NULL, but

OpenSSL does not correctly check for this case. This can lead to a NULL pointer

dereference that results in OpenSSL crashing. If an application processes PKCS12

files from an untrusted source using the OpenSSL APIs then that application will

be vulnerable to this issue.

OpenSSL APIs that are vulnerable to this are: PKCS12_parse(),

PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes()

and PKCS12_newpass().

We have also fixed a similar issue in SMIME_write_PKCS7(). However since this

function is related to writing data we do not consider it security significant.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

Kunpeng DevKit 24.0.RC1

google/protobuf

3.13.0

HWPSIRT-2022-64635

CVE-2021-22569

5.5

An issue in protobuf-java allowed the interleaving of com.google.protobuf.UnknownFieldSet fields in such a way that would be processed out of order. A small malicious payload can occupy the parser for several minutes by creating large numbers of short-lived objects that cause frequent, repeated pauses. We recommend upgrading libraries beyond the vulnerable versions.

Kunpeng DevKit 24.0.RC1

openEuler:grpc

1.41.1-4.oe2203sp1

HWPSIRT-2023-11604

CVE-2023-33953

7.5

gRPC contains a vulnerability that allows hpack table accounting errors could lead to unwanted disconnects between clients and servers in exceptional cases/ Three vectors were found that allow the following DOS attacks:

- Unbounded memory buffering in the HPACK parser

- Unbounded CPU consumption in the HPACK parser

The unbounded CPU consumption is down to a copy that occurred per-input-block in the parser, and because that could be unbounded due to the memory copy bug we end up with an O(n^2) parsing loop, with n selected by the client.

The unbounded memory buffering bugs:

- The header size limit check was behind the string reading code, so we needed to first buffer up to a 4 gigabyte string before rejecting it as longer than 8 or 16kb.

- HPACK varints have an encoding quirk whereby an infinite number of 0’s can be added at the start of an integer. gRPC’s hpack parser needed to read all of them before concluding a parse.

- gRPC’s metadata overflow check was performed per frame, so that the following sequence of frames could cause infinite buffering: HEADERS: containing a: 1 CONTINUATION: containing a: 2 CONTINUATION: containing a: 3 etc…

Kunpeng DevKit 24.0.RC1

OpenSSL

3.0.9

HWPSIRT-2023-24621

CVE-2023-4807

7.8

Issue summary: The POLY1305 MAC (message authentication code) implementation

contains a bug that might corrupt the internal state of applications on the

Windows 64 platform when running on newer X86_64 processors supporting the

AVX512-IFMA instructions.

Impact summary: If in an application that uses the OpenSSL library an attacker

can influence whether the POLY1305 MAC algorithm is used, the application

state might be corrupted with various application dependent consequences.

The POLY1305 MAC (message authentication code) implementation in OpenSSL does

not save the contents of non-volatile XMM registers on Windows 64 platform

when calculating the MAC of data larger than 64 bytes. Before returning to

the caller all the XMM registers are set to zero rather than restoring their

previous content. The vulnerable code is used only on newer x86_64 processors

supporting the AVX512-IFMA instructions.

The consequences of this kind of internal application state corruption can

be various - from no consequences, if the calling application does not

depend on the contents of non-volatile XMM registers at all, to the worst

consequences, where the attacker could get complete control of the application

process. However given the contents of the registers are just zeroized so

the attacker cannot put arbitrary values inside, the most likely consequence,

if any, would be an incorrect result of some application dependent

calculations or a crash leading to a denial of service.

The POLY1305 MAC algorithm is most frequently used as part of the

CHACHA20-POLY1305 AEAD (authenticated encryption with associated data)

algorithm. The most common usage of this AEAD cipher is with TLS protocol

versions 1.2 and 1.3 and a malicious client can influence whether this AEAD

cipher is used by the server. This implies that server applications using

OpenSSL can be potentially impacted. However we are currently not aware of

any concrete application that would be affected by this issue therefore we

consider this a Low severity security issue.

As a workaround the AVX512-IFMA instructions support can be disabled at

runtime by setting the environment variable OPENSSL_ia32cap:

OPENSSL_ia32cap=:~0x200000

The FIPS provider is not affected by this issue.

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2024-34558

CVE-2023-6597

7.8

An issue was found in the CPython `tempfile.TemporaryDirectory` class affecting versions 3.12.1, 3.11.7, 3.10.13, 3.9.18, and 3.8.18 and prior.

The tempfile.TemporaryDirectory class would dereference symlinks during cleanup of permissions-related errors. This means users which can run privileged programs are potentially able to modify permissions of files referenced by symlinks in some circumstances.

Kunpeng DevKit 24.0.RC1

nginx

1.25.4

HWPSIRT-2024-86937

CVE-2024-31079

4.8

When NGINX Plus or NGINX OSS are configured to use the HTTP/3 QUIC module, undisclosed HTTP/3 requests can cause NGINX worker processes to terminate or cause other potential impact. This attack requires that a request be specifically timed during the connection draining process, which the attacker has no visibility and limited influence over.

Kunpeng DevKit 24.0.RC2

OpenSSL

3.0.9

HWPSIRT-2023-97265

CVE-2023-5678

5.3

Issue summary: Generating excessively long X9.42 DH keys or checking

excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to

generate an X9.42 DH key may experience long delays. Likewise, applications

that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check()

to check an X9.42 DH key or X9.42 DH parameters may experience long delays.

Where the key or parameters that are being checked have been obtained from

an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817),

DH_check_pub_key() doesn't make any of these checks, and is therefore

vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large

P, it doesn't check for an excessively large Q.

An application that calls DH_generate_key() or DH_check_pub_key() and

supplies a key or parameters obtained from an untrusted source could be

vulnerable to a Denial of Service attack.

DH_generate_key() and DH_check_pub_key() are also called by a number of

other OpenSSL functions. An application calling any of those other

functions may similarly be affected. The other functions affected by this

are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the

"-pubcheck" option, as well as the OpenSSL genpkey command line application.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Kunpeng DevKit 24.0.RC1

OpenSSL

3.0.9

HWPSIRT-2023-48957

CVE-2023-3817

5.3

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex()

or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long

delays. Where the key or parameters that are being checked have been obtained

from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. After fixing

CVE-2023-3446 it was discovered that a large q parameter value can also trigger

an overly long computation during some of these checks. A correct q value,

if present, cannot be larger than the modulus p parameter, thus it is

unnecessary to perform these checks if q is larger than p.

An application that calls DH_check() and supplies a key or parameters obtained

from an untrusted source could be vulnerable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions.

An application calling any of those other functions may similarly be affected.

The other functions affected by this are DH_check_ex() and

EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications

when using the "-check" option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Kunpeng DevKit 24.0.RC1

OpenSSL

3.0.9

HWPSIRT-2024-27808

CVE-2024-4741

8.1

** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided.

Kunpeng DevKit 24.0.RC2

Python

3.9.11

HWPSIRT-2022-65415

CVE-2022-37454

9.8

The Keccak XKCP SHA-3 reference implementation before fdc6fef has an integer overflow and resultant buffer overflow that allows attackers to execute arbitrary code or eliminate expected cryptographic properties. This occurs in the sponge function interface.

Kunpeng DevKit 24.0.RC1

openEuler:c-ares

1.18.1-5.oe2203sp1

HWPSIRT-2023-65244

CVE-2023-31130

6.4

c-ares is an asynchronous resolver library. ares_inet_net_pton() is vulnerable to a buffer underflow for certain ipv6 addresses, in particular "0::00:00:00/2" was found to cause an issue. C-ares only uses this function internally for configuration purposes which would require an administrator to configure such an address via ares_set_sortlist(). However, users may externally use ares_inet_net_pton() for other purposes and thus be vulnerable to more severe issues. This issue has been fixed in 1.19.1.

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2023-87253

CVE-2023-24329

7.5

An issue in the urllib.parse component of Python before 3.11.4 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters.

Kunpeng DevKit 24.0.RC1

openEuler:sqlite

3.37.2-5.oe2203sp1

HWPSIRT-2023-26427

CVE-2023-7104

7.3

A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.

Kunpeng DevKit 24.0.RC1

openEuler:c-ares

1.18.1-5.oe2203sp1

HWPSIRT-2023-50338

CVE-2023-31124

3.7

c-ares is an asynchronous resolver library. When cross-compiling c-ares and using the autotools build system, CARES_RANDOM_FILE will not be set, as seen when cross compiling aarch64 android. This will downgrade to using rand() as a fallback which could allow an attacker to take advantage of the lack of entropy by not using a CSPRNG. This issue was patched in version 1.19.1.

Kunpeng DevKit 24.0.RC1

OpenSSL

3.0.9

HWPSIRT-2024-73380

CVE-2024-4603

5.3

Issue summary: Checking excessively long DSA keys or parameters may be very

slow.

Impact summary: Applications that use the functions EVP_PKEY_param_check()

or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may

experience long delays. Where the key or parameters that are being checked

have been obtained from an untrusted source this may lead to a Denial of

Service.

The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform

various checks on DSA parameters. Some of those computations take a long time

if the modulus (`p` parameter) is too large.

Trying to use a very large modulus is slow and OpenSSL will not allow using

public keys with a modulus which is over 10,000 bits in length for signature

verification. However the key and parameter check functions do not limit

the modulus size when performing the checks.

An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check()

and supplies a key or parameters obtained from an untrusted source could be

vulnerable to a Denial of Service attack.

These functions are not called by OpenSSL itself on untrusted DSA keys so

only applications that directly call these functions may be vulnerable.

Also vulnerable are the OpenSSL pkey and pkeyparam command line applications

when using the `-check` option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.

Kunpeng DevKit 24.0.RC2

OpenSSL

3.0.9

HWPSIRT-2024-09137

CVE-2024-2511

5.9

Issue summary: Some non-default TLS server configurations can cause unbounded

memory growth when processing TLSv1.3 sessions

Impact summary: An attacker may exploit certain server configurations to trigger

unbounded memory growth that would lead to a Denial of Service

This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is

being used (but not if early_data support is also configured and the default

anti-replay protection is in use). In this case, under certain conditions, the

session cache can get into an incorrect state and it will fail to flush properly

as it fills. The session cache will continue to grow in an unbounded manner. A

malicious client could deliberately create the scenario for this failure to

force a Denial of Service. It may also happen by accident in normal operation.

This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS

clients.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL

1.0.2 is also not affected by this issue.

Kunpeng DevKit 24.0.RC2

Python

3.9.11

HWPSIRT-2023-73521

CVE-2023-27043

5.3

The email module of Python through 3.11.3 incorrectly parses e-mail addresses that contain a special character. The wrong portion of an RFC2822 header is identified as the value of the addr-spec. In some applications, an attacker can bypass a protection mechanism in which application access is granted only after verifying receipt of e-mail to a specific domain (e.g., only @company.example.com addresses may be used for signup). This occurs in email/_parseaddr.py in recent versions of Python.

Kunpeng DevKit 24.0.RC1

openEuler:c-ares

1.18.1-5.oe2203sp1

HWPSIRT-2023-80589

CVE-2023-32067

7.5

c-ares is an asynchronous resolver library. c-ares is vulnerable to denial of service. If a target resolver sends a query, the attacker forges a malformed UDP packet with a length of 0 and returns them to the target resolver. The target resolver erroneously interprets the 0 length as a graceful shutdown of the connection. This issue has been patched in version 1.19.1.

Kunpeng DevKit 24.0.RC1

OpenSSL

3.0.9

HWPSIRT-2024-11517

CVE-2023-6237

5.9

This update for openssl-3 fixes the following issues: * CVE-2023-6129: Fixed vector register clobbering on PowerPC. (bsc#1218690) * CVE-2023-6237: Fixed excessive time spent checking invalid RSA public keys. (bsc#1218810) * CVE-2024-0727: Denial of service when processing a maliciously formatted PKCS12 file (bsc#1219243). ##

Kunpeng DevKit 24.0.RC1

openEuler:grpc

1.41.1-4.oe2203sp1

HWPSIRT-2023-03396

CVE-2023-4785

7.5

Lack of error handling in the TCP server in Google's gRPC starting version 1.23 on posix-compatible platforms (ex. Linux) allows an attacker to cause a denial of service by initiating a significant number of connections with the server. Note that gRPC C++ Python, and Ruby are affected, but gRPC Java, and Go are NOT affected.

Kunpeng DevKit 24.0.RC1

nginx

1.25.4

HWPSIRT-2024-83286

CVE-2024-35200

5.3

When NGINX Plus or NGINX OSS are configured to use the HTTP/3 QUIC module, undisclosed HTTP/3 requests can cause NGINX worker processes to terminate.

Kunpeng DevKit 24.0.RC2

OpenSSL

3.0.9

HWPSIRT-2024-78218

CVE-2023-6129

6.5

Issue summary: The POLY1305 MAC (message authentication code) implementation

contains a bug that might corrupt the internal state of applications running

on PowerPC CPU based platforms if the CPU provides vector instructions.

Impact summary: If an attacker can influence whether the POLY1305 MAC

algorithm is used, the application state might be corrupted with various

application dependent consequences.

The POLY1305 MAC (message authentication code) implementation in OpenSSL for

PowerPC CPUs restores the contents of vector registers in a different order

than they are saved. Thus the contents of some of these vector registers

are corrupted when returning to the caller. The vulnerable code is used only

on newer PowerPC processors supporting the PowerISA 2.07 instructions.

The consequences of this kind of internal application state corruption can

be various - from no consequences, if the calling application does not

depend on the contents of non-volatile XMM registers at all, to the worst

consequences, where the attacker could get complete control of the application

process. However unless the compiler uses the vector registers for storing

pointers, the most likely consequence, if any, would be an incorrect result

of some application dependent calculations or a crash leading to a denial of

service.

The POLY1305 MAC algorithm is most frequently used as part of the

CHACHA20-POLY1305 AEAD (authenticated encryption with associated data)

algorithm. The most common usage of this AEAD cipher is with TLS protocol

versions 1.2 and 1.3. If this cipher is enabled on the server a malicious

client can influence whether this AEAD cipher is used. This implies that

TLS server applications using OpenSSL can be potentially impacted. However

we are currently not aware of any concrete application that would be affected

by this issue therefore we consider this a Low severity security issue.

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2019-14711

CVE-2007-4559

6.8

Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2022-60937

CVE-2015-20107

7.6

In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2024-51481

CVE-2024-0450

6.2

An issue was found in the CPython `zipfile` module affecting versions 3.12.1, 3.11.7, 3.10.13, 3.9.18, and 3.8.18 and prior.

The zipfile module is vulnerable to “quoted-overlap” zip-bombs which exploit the zip format to create a zip-bomb with a high compression ratio. The fixed versions of CPython makes the zipfile module reject zip archives which overlap entries in the archive.

Kunpeng DevKit 24.0.RC1

google/protobuf

3.13.0

HWPSIRT-2022-13426

CVE-2021-22570

5.5

Nullptr dereference when a null char is present in a proto symbol. The symbol is parsed incorrectly, leading to an unchecked call into the proto file's name during generation of the resulting error message. Since the symbol is incorrectly parsed, the file is nullptr. We recommend upgrading to version 3.15.0 or greater.

Kunpeng DevKit 24.0.RC1

Python

3.9.11

HWPSIRT-2022-65549

CVE-2020-10735

7.5

A flaw was found in python. In algorithms with quadratic time complexity using non-binary bases, when using int("text"), a system could take 50ms to parse an int string with 100,000 digits and 5s for 1,000,000 digits (float, decimal, int.from_bytes(), and int() for binary bases 2, 4, 8, 16, and 32 are not affected). The highest threat from this vulnerability is to system availability.

Kunpeng DevKit 24.0.RC1

nginx

1.25.4

HWPSIRT-2024-59916

CVE-2024-32760

6.5

When NGINX Plus or NGINX OSS are configured to use the HTTP/3 QUIC module, undisclosed HTTP/3 encoder instructions can cause NGINX worker processes to terminate or cause or other potential impact.

Kunpeng DevKit 24.0.RC2

Python

3.9.11

HWPSIRT-2022-48740

CVE-2022-45061

7.5

An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16.

Kunpeng DevKit 24.0.RC1

OpenSSL

3.0.9

HWPSIRT-2023-90147

CVE-2023-2975

5.3

Issue summary: The AES-SIV cipher implementation contains a bug that causes

it to ignore empty associated data entries which are unauthenticated as

a consequence.

Impact summary: Applications that use the AES-SIV algorithm and want to

authenticate empty data entries as associated data can be mislead by removing

adding or reordering such empty entries as these are ignored by the OpenSSL

implementation. We are currently unaware of any such applications.

The AES-SIV algorithm allows for authentication of multiple associated

data entries along with the encryption. To authenticate empty data the

application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with

NULL pointer as the output buffer and 0 as the input buffer length.

The AES-SIV implementation in OpenSSL just returns success for such a call

instead of performing the associated data authentication operation.

The empty data thus will not be authenticated.

As this issue does not affect non-empty associated data authentication and

we expect it to be rare for an application to use empty associated data

entries this is qualified as Low severity issue.

Kunpeng DevKit 24.0.RC1