漏洞修补列表

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

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

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.

BeiMing 24.2.RC3

Apache Hadoop

3.3.1

HWPSIRT-2022-20495

CVE-2021-25642

8.8

ZKConfigurationStore which is optionally used by CapacityScheduler of Apache Hadoop YARN deserializes data obtained from ZooKeeper without validation. An attacker having access to ZooKeeper can run arbitrary commands as YARN user by exploiting this. Users should upgrade to Apache Hadoop 2.10.2, 3.2.4, 3.3.4 or later (containing YARN-11126) if ZKConfigurationStore is used.

BeiMing 24.2.RC3

Apache Hadoop

3.3.1

HWPSIRT-2022-84454

CVE-2022-26612

9.8

In Apache Hadoop, The unTar function uses unTarUsingJava function on Windows and the built-in tar utility on Unix and other OSes. As a result, a TAR entry may create a symlink under the expected extraction directory which points to an external directory. A subsequent TAR entry may extract an arbitrary file into the external directory using the symlink name. This however would be caught by the same targetDirPath check on Unix because of the getCanonicalPath call. However on Windows, getCanonicalPath doesn't resolve symbolic links, which bypasses the check. unpackEntries during TAR extraction follows symbolic links which allows writing outside expected base directory on Windows. This was addressed in Apache Hadoop 3.2.3

BeiMing 24.2.RC3

Apache Hadoop

3.3.1

HWPSIRT-2022-49438

CVE-2021-37404

9.8

There is a potential heap buffer overflow in Apache Hadoop libhdfs native code. Opening a file path provided by user without validation may result in a denial of service or arbitrary code execution. Users should upgrade to Apache Hadoop 2.10.2, 3.2.3, 3.3.2 or higher.

BeiMing 24.2.RC3

Apache Hadoop

3.3.1

HWPSIRT-2022-60326

CVE-2021-33036

8.8

In Apache Hadoop 2.2.0 to 2.10.1, 3.0.0-alpha1 to 3.1.4, 3.2.0 to 3.2.2, and 3.3.0 to 3.3.1, a user who can escalate to yarn user can possibly run arbitrary commands as root user. Users should upgrade to Apache Hadoop 2.10.2, 3.2.3, 3.3.2 or higher.

BeiMing 24.2.RC3

Apache Hadoop

3.3.1

HWPSIRT-2022-34903

CVE-2022-25168

9.8

Apache Hadoop's FileUtil.unTar(File, File) API does not escape the input file name before being passed to the shell. An attacker can inject arbitrary commands. This is only used in Hadoop 3.3 InMemoryAliasMap.completeBootstrapTransfer, which is only ever run by a local user. It has been used in Hadoop 2.x for yarn localization, which does enable remote code execution. It is used in Apache Spark, from the SQL command ADD ARCHIVE. As the ADD ARCHIVE command adds new binaries to the classpath, being able to execute shell scripts does not confer new permissions to the caller. SPARK-38305. "Check existence of file before untarring/zipping", which is included in 3.3.0, 3.1.4, 3.2.2, prevents shell commands being executed, regardless of which version of the hadoop libraries are in use. Users should upgrade to Apache Hadoop 2.10.2, 3.2.4, 3.3.3 or upper (including HADOOP-18136).

BeiMing 24.2.RC3

Apache Hadoop

3.3.1

HWPSIRT-2023-14825

CVE-2023-26031

7.5

Relative library resolution in linux container-executor binary in Apache Hadoop 3.3.1-3.3.4 on Linux allows local user to gain root privileges. If the YARN cluster is accepting work from remote (authenticated) users, this MAY permit remote users to gain root privileges. Hadoop 3.3.0 updated the " YARN Secure Containers https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/SecureContainer.html " to add a feature for executing user-submitted applications in isolated linux containers. The native binary HADOOP_HOME/bin/container-executor is used to launch these containers; it must be owned by root and have the suid bit set in order for the YARN processes to run the containers as the specific users submitting the jobs. The patch " YARN-10495 https://issues.apache.org/jira/browse/YARN-10495 . make the rpath of container-executor configurable" modified the library loading path for loading .so files from "$ORIGIN/" to ""$ORIGIN/:../lib/native/". This is the a path through which libcrypto.so is located. Thus it is is possible for a user with reduced privileges to install a malicious libcrypto library into a path to which they have write access, invoke the container-executor command, and have their modified library executed as root. If the YARN cluster is accepting work from remote (authenticated) users, and these users' submitted job are executed in the physical host, rather than a container, then the CVE permits remote users to gain root privileges. The fix for the vulnerability is to revert the change, which is done in YARN-11441 https://issues.apache.org/jira/browse/YARN-11441 , "Revert YARN-10495". This patch is in hadoop-3.3.5. To determine whether a version of container-executor is vulnerable, use the readelf command. If the RUNPATH or RPATH value contains the relative path "./lib/native/" then it is at risk $ readelf -d container-executor|grep 'RUNPATH\|RPATH' 0x000000000000001d (RUNPATH) Library runpath: [$ORIGIN/:../lib/native/] If it does not, then it is safe: $ readelf -d container-executor|grep 'RUNPATH\|RPATH' 0x000000000000001d (RUNPATH) Library runpath: [$ORIGIN/] For an at-risk version of container-executor to enable privilege escalation, the owner must be root and the suid bit must be set $ ls -laF /opt/hadoop/bin/container-executor ---Sr-s---. 1 root hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor A safe installation lacks the suid bit; ideally is also not owned by root. $ ls -laF /opt/hadoop/bin/container-executor -rwxr-xr-x. 1 yarn hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor This configuration does not support Yarn Secure Containers, but all other hadoop services, including YARN job execution outside secure containers continue to work.

BeiMing 24.2.RC3