漏洞修复列表

google/protobuf

3.13.0

CVE-2021-22570

0.0

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.

MindStudio 7.0.RC1

google/protobuf

3.13.0

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.

MindStudio 7.0.RC1

google/protobuf

3.13.0

CVE-2021-22569

0.0

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.

MindStudio 7.0.RC1

OpenSSL

3.0.9

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.

MindStudio 7.0.RC1

SQLite

3.40.1

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.

MindStudio 7.0.RC1

OpenSSL

3.0.9

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.

MindStudio 7.0.RC1

IntelliJ IDEA - Community Edition

2022.3.2

CVE-2022-48433

7.5

In JetBrains IntelliJ IDEA before 2023.1 the NTLM hash could leak through an API method used in the IntelliJ IDEA built-in web server.

MindStudio 7.0.RC1

openEuler:ncurses

6.3-5.oe2203sp1

CVE-2023-29491

7.8

ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.

MindStudio 7.0.RC1

openEuler:ncurses

6.3-5.oe2203sp1

CVE-2023-50495

6.5

NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().

MindStudio 7.0.RC1

OpenSSL

3.0.9

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.

MindStudio 7.0.RC1

IntelliJ IDEA - Community Edition

2022.3.2

CVE-2022-48431

7.8

In JetBrains IntelliJ IDEA before 2023.1 in some cases, Gradle and Maven projects could be imported without the “Trust Project” confirmation.

MindStudio 7.0.RC1

IntelliJ IDEA - Community Edition

2022.3.2

CVE-2022-48430

7.5

In JetBrains IntelliJ IDEA before 2023.1 file content could be disclosed via an external stylesheet path in Markdown preview.

MindStudio 7.0.RC1

OpenSSL

3.0.9

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.

MindStudio 7.0.RC1

IntelliJ IDEA - Community Edition

2022.3.2

CVE-2023-38069

3.3

In JetBrains IntelliJ IDEA before 2023.1.4 license dialog could be suppressed in certain cases

MindStudio 7.0.RC1

IntelliJ IDEA - Community Edition

2022.3.2

CVE-2022-48432

8.8

In JetBrains IntelliJ IDEA before 2023.1 the bundled version of Chromium wasn't sandboxed.

MindStudio 7.0.RC1

OpenSSL

3.0.9

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.

MindStudio 7.0.RC1

OpenSSL

3.0.9

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.

MindStudio 7.0.RC1

OpenSSL

3.0.9

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). ##

MindStudio 7.0.RC1

openEuler:ncurses

6.3-5.oe2203sp1

CVE-2023-45918

3.3

ncurses 6.4-20230610 has a NULL pointer dereference in tgetstr in tinfo/lib_termcap.c.

MindStudio 7.0.RC1

OpenSSL

3.0.9

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.

MindStudio 7.0.RC1

OpenSSL

3.0.9

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.

MindStudio 7.0.RC1