漏洞修补列表

UTBotJava

2023.10

HWPSIRT-2021-28415

CVE-2021-45046

9.0

在Apache Log4j 2.0-2.15.0版本中（不含2.12.2），当日志使用的非默认的PatternLayout中包含Context Lookup(如$${ctx:loginId})时，攻击者输入包含JNDI Lookup模式的恶意字符串到日志中，可能导致信息泄露、部分环境下的远程代码执行和所有环境下的本地代码执行。该CVE代号为CVE-2021-45046，CVSS评分9.0分。

In Apache Log4j2 versions up to and including 2.15.0 (excluding security release 2.12.2), when the logging configuration uses a non-default Pattern Layout with a Context Lookup (for example, $${ctx:loginId}), attackers with control over Thread Context Map (MDC) input data can craft malicious input data using a JNDI Lookup pattern, resulting in an information leak and remote code execution in some environments and local code execution in all environments. This is assigned with CVE-2021-45046, the CVSS score is 9.0.

Kunpeng DevKit 25.0.0

Python

3.11.4

HWPSIRT-2024-55339

CVE-2024-9287

7.8

A vulnerability has been found in the CPython `venv` module and CLI where path names provided when creating a virtual environment were not quoted properly, allowing the creator to inject commands into virtual environment "activation" scripts (ie "source venv/bin/activate"). This means that attacker-controlled virtual environments are able to run commands when the virtual environment is activated. Virtual environments which are not created by an attacker or which aren't activated before being used (ie "./venv/bin/python") are not affected.

Kunpeng DevKit 25.0.0

Python

3.11.4

HWPSIRT-2023-03320

CVE-2023-41105

7.5

An issue was discovered in Python 3.11 through 3.11.4. If a path containing '\0' bytes is passed to os.path.normpath(), the path will be truncated unexpectedly at the first '\0' byte. There are plausible cases in which an application would have rejected a filename for security reasons in Python 3.10.x or earlier, but that filename is no longer rejected in Python 3.11.x.

Kunpeng DevKit 25.0.0

nginx

1.27.1

HWPSIRT-2025-41823

CVE-2025-23419

4.3

When multiple server blocks are configured to share the same IP address and port, an attacker can use session resumption to bypass client certificate authentication requirements on these servers. This vulnerability arises when TLS Session Tickets https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_session_ticket_key are used and/or the SSL session cache https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_session_cache are used in the default server and the default server is performing client certificate authentication.

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Kunpeng DevKit 25.0.0

Python

3.11.4

HWPSIRT-2024-69283

CVE-2024-0397

7.4

A defect was discovered in the Python “ssl” module where there is a memory

race condition with the ssl.SSLContext methods “cert_store_stats()” and

“get_ca_certs()”. The race condition can be triggered if the methods are

called at the same time as certificates are loaded into the SSLContext,

such as during the TLS handshake with a certificate directory configured.

This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.

Kunpeng DevKit 25.0.0

Python

3.11.4

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 25.0.0

Python

3.11.4

HWPSIRT-2024-01158

CVE-2024-7592

7.5

There is a LOW severity vulnerability affecting CPython, specifically the

'http.cookies' standard library module.

When parsing cookies that contained backslashes for quoted characters in

the cookie value, the parser would use an algorithm with quadratic

complexity, resulting in excess CPU resources being used while parsing the

value.

Kunpeng DevKit 25.0.0

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 25.0.0

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 25.0.0

openEuler:bcc

0.29.1-2.oe2403

HWPSIRT-2024-68765

CVE-2024-2314

2.8

If kernel headers need to be extracted, bcc will attempt to load them from a temporary directory. An unprivileged attacker could use this to force bcc to load compromised linux headers. Linux distributions which provide kernel headers by default are not affected by default.

Kunpeng DevKit 25.0.0

UTBotJava

2023.10

HWPSIRT-2021-94301

CVE-2021-44228

10.0

在Apache Log4j 2.0-2.14.1版本中（不含2.12.2），JNDI功能可能在配置文件、日志信息和一些参数中可能存在对LDAP和其他JNDI协议保护不足的问题。攻击者如果可以控制日志信息或参数则可能导致通过LDAP服务器执行任意代码。该CVE代号为CVE-2021-44228，CVSS评分10.0分。In Apache Log4j2 versions up to and including 2.14.1 (excluding security release 2.12.2), the JNDI features used in configurations, log messages, and parameters do not protect against attacker-controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. This is assigned with CVE-2021-44228, the CVSS score is 10.0.

Kunpeng DevKit 25.0.0

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 25.0.0

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 25.0.0

Python

3.11.4

HWPSIRT-2025-35644

CVE-2025-1795

3.1

During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected behavior is that the separating comma remains a plan comma. This can result in the address header being misinterpreted by some mail servers.

Kunpeng DevKit 25.0.0

OpenSSL

3.0.9

HWPSIRT-2025-34581

CVE-2024-13176

4.1

Issue summary: A timing side-channel which could potentially allow recovering

the private key exists in the ECDSA signature computation.

Impact summary: A timing side-channel in ECDSA signature computations

could allow recovering the private key by an attacker. However, measuring

the timing would require either local access to the signing application or

a very fast network connection with low latency.

There is a timing signal of around 300 nanoseconds when the top word of

the inverted ECDSA nonce value is zero. This can happen with significant

probability only for some of the supported elliptic curves. In particular

the NIST P-521 curve is affected. To be able to measure this leak, the attacker

process must either be located in the same physical computer or must

have a very fast network connection with low latency. For that reason

the severity of this vulnerability is Low.

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

Kunpeng DevKit 25.0.0

Python

3.11.4

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 25.0.0

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 25.0.0

OpenSSL

3.0.9

HWPSIRT-2024-27808

CVE-2024-4741

7.5

Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause

memory to be accessed that was previously freed in some situations

Impact summary: A use after free can have a range of potential consequences such

as the corruption of valid data, crashes or execution of arbitrary code.

However, only applications that directly call the SSL_free_buffers function are

affected by this issue. Applications that do not call this function are not

vulnerable. Our investigations indicate that this function is rarely used by

applications.

The SSL_free_buffers function is used to free the internal OpenSSL buffer used

when processing an incoming record from the network. The call is only expected

to succeed if the buffer is not currently in use. However, two scenarios have

been identified where the buffer is freed even when still in use.

The first scenario occurs where a record header has been received from the

network and processed by OpenSSL, but the full record body has not yet arrived.

In this case calling SSL_free_buffers will succeed even though a record has only

been partially processed and the buffer is still in use.

The second scenario occurs where a full record containing application data has

been received and processed by OpenSSL but the application has only read part of

this data. Again a call to SSL_free_buffers will succeed even though the buffer

is still in use.

While these scenarios could occur accidentally during normal operation a

malicious attacker could attempt to engineer a stituation where this occurs.

We are not aware of this issue being actively exploited.

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

Kunpeng DevKit 25.0.0

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 25.0.0

openEuler:grpc

1.60.0-2.oe2403

HWPSIRT-2024-57424

CVE-2024-11407

5.8

There exists a denial of service through Data corruption in gRPC-C++ - gRPC-C++ servers with transmit zero copy enabled through the channel arg GRPC_ARG_TCP_TX_ZEROCOPY_ENABLED can experience data corruption issues. The data sent by the application may be corrupted before transmission over the network thus leading the receiver to receive an incorrect set of bytes causing RPC requests to fail. We recommend upgrading past commit e9046b2bbebc0cb7f5dc42008f807f6c7e98e791

Kunpeng DevKit 25.0.0

OpenSSL

3.0.9

HWPSIRT-2024-40724

CVE-2024-6119

7.5

Issue summary: Applications performing certificate name checks (e.g., TLS

clients checking server certificates) may attempt to read an invalid memory

address resulting in abnormal termination of the application process.

Impact summary: Abnormal termination of an application can a cause a denial of

service.

Applications performing certificate name checks (e.g., TLS clients checking

server certificates) may attempt to read an invalid memory address when

comparing the expected name with an `otherName` subject alternative name of an

X.509 certificate. This may result in an exception that terminates the

application program.

Note that basic certificate chain validation (signatures, dates, ...) is not

affected, the denial of service can occur only when the application also

specifies an expected DNS name, Email address or IP address.

TLS servers rarely solicit client certificates, and even when they do, they

generally don't perform a name check against a reference identifier (expected

identity), but rather extract the presented identity after checking the

certificate chain. So TLS servers are generally not affected and the severity

of the issue is Moderate.

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

Kunpeng DevKit 25.0.0

OpenSSL

3.0.9

HWPSIRT-2024-07658

CVE-2024-9143

4.3

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted

explicit values for the field polynomial can lead to out-of-bounds memory reads

or writes.

Impact summary: Out of bound memory writes can lead to an application crash or

even a possibility of a remote code execution, however, in all the protocols

involving Elliptic Curve Cryptography that we're aware of, either only "named

curves" are supported, or, if explicit curve parameters are supported, they

specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent

problematic input values. Thus the likelihood of existence of a vulnerable

application is low.

In particular, the X9.62 encoding is used for ECC keys in X.509 certificates,

so problematic inputs cannot occur in the context of processing X.509

certificates. Any problematic use-cases would have to be using an "exotic"

curve encoding.

The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),

and various supporting BN_GF2m_*() functions.

Applications working with "exotic" explicit binary (GF(2^m)) curve parameters,

that make it possible to represent invalid field polynomials with a zero

constant term, via the above or similar APIs, may terminate abruptly as a

result of reading or writing outside of array bounds. Remote code execution

cannot easily be ruled out.

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

Kunpeng DevKit 25.0.0

OpenSSL

3.0.9

HWPSIRT-2024-55293

CVE-2024-5535

9.1

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an

empty supported client protocols buffer may cause a crash or memory contents to

be sent to the peer.

Impact summary: A buffer overread can have a range of potential consequences

such as unexpected application beahviour or a crash. In particular this issue

could result in up to 255 bytes of arbitrary private data from memory being sent

to the peer leading to a loss of confidentiality. However, only applications

that directly call the SSL_select_next_proto function with a 0 length list of

supported client protocols are affected by this issue. This would normally never

be a valid scenario and is typically not under attacker control but may occur by

accident in the case of a configuration or programming error in the calling

application.

The OpenSSL API function SSL_select_next_proto is typically used by TLS

applications that support ALPN (Application Layer Protocol Negotiation) or NPN

(Next Protocol Negotiation). NPN is older, was never standardised and

is deprecated in favour of ALPN. We believe that ALPN is significantly more

widely deployed than NPN. The SSL_select_next_proto function accepts a list of

protocols from the server and a list of protocols from the client and returns

the first protocol that appears in the server list that also appears in the

client list. In the case of no overlap between the two lists it returns the

first item in the client list. In either case it will signal whether an overlap

between the two lists was found. In the case where SSL_select_next_proto is

called with a zero length client list it fails to notice this condition and

returns the memory immediately following the client list pointer (and reports

that there was no overlap in the lists).

This function is typically called from a server side application callback for

ALPN or a client side application callback for NPN. In the case of ALPN the list

of protocols supplied by the client is guaranteed by libssl to never be zero in

length. The list of server protocols comes from the application and should never

normally be expected to be of zero length. In this case if the

SSL_select_next_proto function has been called as expected (with the list

supplied by the client passed in the client/client_len parameters), then the

application will not be vulnerable to this issue. If the application has

accidentally been configured with a zero length server list, and has

accidentally passed that zero length server list in the client/client_len

parameters, and has additionally failed to correctly handle a "no overlap"

response (which would normally result in a handshake failure in ALPN) then it

will be vulnerable to this problem.

In the case of NPN, the protocol permits the client to opportunistically select

a protocol when there is no overlap. OpenSSL returns the first client protocol

in the no overlap case in support of this. The list of client protocols comes

from the application and should never normally be expected to be of zero length.

However if the SSL_select_next_proto function is accidentally called with a

client_len of 0 then an invalid memory pointer will be returned instead. If the

application uses this output as the opportunistic protocol then the loss of

confidentiality will occur.

This issue has been assessed as Low severity because applications are most

likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not

widely used. It also requires an application configuration or programming error.

Finally, this issue would not typically be under attacker control making active

exploitation unlikely.

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

Due to the low severity of this issue we are not issuing new releases of

OpenSSL at this time. The fix will be included in the next releases when they

become available.

Kunpeng DevKit 25.0.0

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 25.0.0

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 25.0.0

OpenSSL

3.0.9

HWPSIRT-2024-11517

CVE-2023-6237

5.9

Issue summary: Checking excessively long invalid RSA public keys may take

a long time.

Impact summary: Applications that use the function EVP_PKEY_public_check()

to check RSA public keys may experience long delays. Where the key that

is being checked has been obtained from an untrusted source this may lead

to a Denial of Service.

When function EVP_PKEY_public_check() is called on RSA public keys,

a computation is done to confirm that the RSA modulus, n, is composite.

For valid RSA keys, n is a product of two or more large primes and this

computation completes quickly. However, if n is an overly large prime,

then this computation would take a long time.

An application that calls EVP_PKEY_public_check() and supplies an RSA key

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

attack.

The function EVP_PKEY_public_check() is not called from other OpenSSL

functions however it is called from the OpenSSL pkey command line

application. For that reason that application is also vulnerable if used

with the '-pubin' and '-check' options on untrusted data.

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 25.0.0

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 25.0.0

Python

3.11.4

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 25.0.0

Python

3.11.4

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 25.0.0

openEuler:grpc

1.60.0-2.oe2403

HWPSIRT-2024-56642

CVE-2024-7246

5.8

It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It's also possible to use this vulnerability to leak other clients HTTP header keys, but not values.

This occurs because the error status for a misencoded header is not cleared between header reads, resulting in subsequent (incrementally indexed) added headers in the first request being poisoned until cleared from the HPACK table.

Please update to a fixed version of gRPC as soon as possible. This bug has been fixed in 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4.

Kunpeng DevKit 25.0.0

Python

3.11.4

HWPSIRT-2024-68388

CVE-2024-6232

7.5

There is a MEDIUM severity vulnerability affecting CPython.

Regular expressions that allowed excessive backtracking during tarfile.TarFile header parsing are vulnerable to ReDoS via specifically-crafted tar archives.

Kunpeng DevKit 25.0.0

openEuler:sqlite

3.37.2-6.oe2203sp3

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 25.0.0

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 misled 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 25.0.0