BlackTreeIndependent security intelligence

← Back to the CVE catalogue

Full vulnerability report · 2023

CVE-2022-4450High confidence

Double free after calling PEM_read_bio_ex

OpenSSL · OpenSSL

7.5HighCVSS 3.1

Recommended action

Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

11 current

SSA-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < V3.1.5

5 known affected

The vendor explicitly identifies these products as affected by this CVE.

SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)
SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)
SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)
SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V3.1.5 or later version

SSA-769027 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-769027: Multiple Vulnerabilities fixed in SCALANCE W700 IEEE 802.11ax devices before V3.0.0

19 known affected

The vendor explicitly identifies these products as affected by this CVE.

SCALANCE WAB762-1 (6GK5762-1AJ00-6AA0)
SCALANCE WAM763-1 (6GK5763-1AL00-7DA0)
SCALANCE WAM763-1 (ME) (6GK5763-1AL00-7DC0)
SCALANCE WAM763-1 (US) (6GK5763-1AL00-7DB0)
SCALANCE WAM766-1 (6GK5766-1GE00-7DA0)
SCALANCE WAM766-1 (ME) (6GK5766-1GE00-7DC0)
SCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0)
SCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0)
SCALANCE WAM766-1 EEC (ME) (6GK5766-1GE00-7TC0)
SCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0)
SCALANCE WUB762-1 (6GK5762-1AJ00-1AA0)
SCALANCE WUB762-1 iFeatures (6GK5762-1AJ00-2AA0)

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V3.0.0 or later version

SSA-337522 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-337522: Multiple Vulnerabilities in TIM 1531 IRC before V2.4.8

2 known affected

The vendor explicitly identifies these products as affected by this CVE.

SIPLUS TIM 1531 IRC (6AG1543-1MX00-7XE0)
TIM 1531 IRC (6GK7543-1MX00-0XE0)

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V2.4.8 or later version

SSA-625862 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-625862: Multiple Vulnerabilities in Third-Party Components in SIMATIC CP 1542SP-1 and CP 1543SP-1 before V2.3

6 known affected

The vendor explicitly identifies these products as affected by this CVE.

SIMATIC CP 1542SP-1 (6GK7542-6UX00-0XE0)
SIMATIC CP 1542SP-1 IRC (6GK7542-6VX00-0XE0)
SIMATIC CP 1543SP-1 (6GK7543-6WX00-0XE0)
SIPLUS ET 200SP CP 1542SP-1 IRC TX RAIL (6AG2542-6VX00-4XE0)
SIPLUS ET 200SP CP 1543SP-1 ISEC (6AG1543-6WX00-7XE0)
SIPLUS ET 200SP CP 1543SP-1 ISEC TX RAIL (6AG2543-6WX00-4XE0)

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V2.3 or later version

SSA-879734 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-879734: Multiple Vulnerabilities in SCALANCE XM-400/XR-500 before V6.6.1

26 known affected

The vendor explicitly identifies these products as affected by this CVE.

SCALANCE XM408-4C (6GK5408-4GP00-2AM2)
SCALANCE XM408-4C (L3 int.) (6GK5408-4GQ00-2AM2)
SCALANCE XM408-8C (6GK5408-8GS00-2AM2)
SCALANCE XM408-8C (L3 int.) (6GK5408-8GR00-2AM2)
SCALANCE XM416-4C (6GK5416-4GS00-2AM2)
SCALANCE XM416-4C (L3 int.) (6GK5416-4GR00-2AM2)
SCALANCE XR524-8C, 1x230V (6GK5524-8GS00-3AR2)
SCALANCE XR524-8C, 1x230V (L3 int.) (6GK5524-8GR00-3AR2)
SCALANCE XR524-8C, 24V (6GK5524-8GS00-2AR2)
SCALANCE XR524-8C, 24V (L3 int.) (6GK5524-8GR00-2AR2)
SCALANCE XR524-8C, 2x230V (6GK5524-8GS00-4AR2)
SCALANCE XR524-8C, 2x230V (L3 int.) (6GK5524-8GR00-4AR2)

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V6.6.1 or later version

SSA-203374 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-203374: Multiple OpenSSL Vulnerabilities in SCALANCE W1750D Devices

3 known affected

The vendor explicitly identifies these products as affected by this CVE.

SCALANCE W1750D (JP) (6GK5750-2HX01-1AD0)
SCALANCE W1750D (ROW) (6GK5750-2HX01-1AA0)
SCALANCE W1750D (USA) (6GK5750-2HX01-1AB0)

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V8.10.0.9 or later version The update is available upon request from customer support

SSA-556635 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-556635: Multiple Vulnerabilities in Telecontrol Server Basic before V3.1.2.0

1 known affected

The vendor explicitly identifies these products as affected by this CVE.

TeleControl Server Basic V3

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V3.1.2 or later version

SSA-794697 · CSAF 2.0 · revision 9 · interimSiemens ProductCERTSSA-794697: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP before V1.1

1 known affected

The vendor explicitly identifies these products as affected by this CVE.

SIMATIC S7-1500 TM MFP - GNU/Linux subsystem

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V1.1 or later version

SSA-699386 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-699386: Multiple Vulnerabilities in SCALANCE XB-200 / XC-200 / XP-200 / XF-200BA / XR-300WG Family before V4.5

71 known affected

The vendor explicitly identifies these products as affected by this CVE.

SCALANCE XB205-3 (SC, PN) (6GK5205-3BB00-2AB2)
SCALANCE XB205-3 (ST, E/IP) (6GK5205-3BB00-2TB2)
SCALANCE XB205-3 (ST, E/IP) (6GK5205-3BD00-2TB2)
SCALANCE XB205-3 (ST, PN) (6GK5205-3BD00-2AB2)
SCALANCE XB205-3LD (SC, E/IP) (6GK5205-3BF00-2TB2)
SCALANCE XB205-3LD (SC, PN) (6GK5205-3BF00-2AB2)
SCALANCE XB208 (E/IP) (6GK5208-0BA00-2TB2)
SCALANCE XB208 (PN) (6GK5208-0BA00-2AB2)
SCALANCE XB213-3 (SC, E/IP) (6GK5213-3BD00-2TB2)
SCALANCE XB213-3 (SC, PN) (6GK5213-3BD00-2AB2)
SCALANCE XB213-3 (ST, E/IP) (6GK5213-3BB00-2TB2)
SCALANCE XB213-3 (ST, PN) (6GK5213-3BB00-2AB2)

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V4.5 or later version

SSA-943925 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-943925: Multiple Vulnerabilities in SINEC NMS before V2.0 SP1

1 known affected

The vendor explicitly identifies these products as affected by this CVE.

SINEC NMS

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V2.0 SP1 or later version

SSA-561322 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-561322: Multiple Vulnerabilities in SIMATIC MV500 Devices before V3.3.4

6 known affected

The vendor explicitly identifies these products as affected by this CVE.

SIMATIC MV540 H (6GF3540-0GE10)
SIMATIC MV540 S (6GF3540-0CD10)
SIMATIC MV550 H (6GF3550-0GE10)
SIMATIC MV550 S (6GF3550-0CD10)
SIMATIC MV560 U (6GF3560-0LE10)
SIMATIC MV560 X (6GF3560-0HE10)

Summary: The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation: Update to V3.3.4 or later version

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current

ENISA EUVD identifier

EUVD-2023-0796

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

01

What, why and how

The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.

What

The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.

Why

The product calls free() twice on the same memory address.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.

Why

The product calls free() twice on the same memory address.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

?

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

?

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → Double Free → disrupt the affected service
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-415 ↗
CWE-415: Double Free. The product calls free() twice on the same memory address.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkUnauthenticatedDenial of serviceCWE-415

A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2023-0796Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2023-1432Siemens SIMATIC S7: Mehrere Schwachstellen

Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter, anonymer, authentisierter, physischer oder lokaler Angreifer kann mehrere Schwachstellen in Siemens SIMATIC S7 ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen, seine Privilegien zu erweitern und Daten zu manipulieren.

Official advisory

BSI · German · WID-SEC-W-2024-0794Dell ECS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell ECS ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode mit Administratorrechten auszuführen, Informationen offenzulegen, Dateien zu manipulieren, einen Cross-Site-Scripting-Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.

Official advisory

BSI · German · WID-SEC-W-2024-0114Oracle Systems: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Systems ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory

BSI · German · WID-SEC-W-2023-1812Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory

BSI · German · WID-SEC-W-2023-1424Xerox FreeFlow Print Server für Solaris: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität des Systems zu gefährden.

Official advisory

BSI · German · WID-SEC-W-2024-1591Juniper JUNOS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Juniper JUNOS ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Privilegien zu erweitern und Sicherheitsmechanismen inklusive zu umgehen.

Official advisory

BSI · German · WID-SEC-W-2023-0304OpenSSL: Mehrere Schwachstellen

Ein entfernter, authentisierter oder anonymer Angreifer kann mehrere Schwachstellen in OpenSSL ausnutzen, um einen Denial of Service Angriff durchzuführen, Informationen offenzulegen oder Chiffretext über ein Netzwerk wiederherzustellen.

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

VERecord?id=CVE-2022-3171 Référence CVE CVE-2022-3509 https://www.cve.org/CVERecord?id=CVE-2022-3509 Référence CVE CVE-2022-3510 https://www.cve.org/CVERecord?id=CVE-2022-3510 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-40023 https://www.cve.org/CVERecord?id=CVE-2022-40023 Référence CVE CVE-2022-40149 https://www.cve.org/CVERecord?id=CVE-2022-40149 Référence CVE CVE-2022-40150 https://www.cve.org/CVERecord?id=CVE-2022-40150 Référence CVE CVE-2022-42003 https://www.cve.org/CVERecord?id=CVE-2022-42003 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-45868 https://www.cve.org/CVERecord?id=CVE-2022-45868 Référence CVE CVE-2022-46337 https://www.cve.org/CVERecord?id=CVE-2022-46337 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-137

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0249Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2022-29154 Référence CVE CVE-2022-29458 https://www.cve.org/CVERecord?id=CVE-2022-29458 Référence CVE CVE-2022-3171 https://www.cve.org/CVERecord?id=CVE-2022-3171 Référence CVE CVE-2022-32743 https://www.cve.org/CVERecord?id=CVE-2022-32743 Référence CVE CVE-2022-3509 https://www.cve.org/CVERecord?id=CVE-2022-3509 Référence CVE CVE-2022-3510 https://www.cve.org/CVERecord?id=CVE-2022-3510 Référence CVE CVE-2022-40609 https://www.cve.org/CVERecord?id=CVE-2022-40609 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-45047 https://www.cve.org/CVERecord?id=CVE-2022-45047 Référence CVE CVE-2022-46337 https://www.cve.org/CVERecord?id=CVE-2022-46337 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-21830 https://www.cve.org/CVERecord?id=CVE-2023-21830 Référence CVE CVE-2023-21843 https://www.cve.org/CVERecord?id=CVE-2023-21843 Référence CVE CVE-2023-21930 https://www.cve.org/CVERecord?id=CVE-2023-21930 Référence CVE CVE-2023-21937 https://www.cve.org/CVERecord?id=CVE-2

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2022-41854 Référence CVE CVE-2022-42003 https://www.cve.org/CVERecord?id=CVE-2022-42003 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-48174 https://www.cve.org/CVERecord?id=CVE-2022-48174 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-0464 Référence CVE CVE-2023-0465 https://www.cve.org/CVERecord?id=CVE-2023-0465

Official advisory

CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2022-40304 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-42898 https://www.cve.org/CVERecord?id=CVE-2022-42898 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43680 https://www.cve.org/CVERecord?id=CVE-2022-43680 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-46908 https://www.cve.org/CVERecord?id=CVE-2022-46908 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=CVE-2022-48632 Référence CVE CVE-2022-48637 https://www.cve.org/CVERecord?id=CVE-2022-48637 Référence CVE CVE-2022-48639 https://www.cve.org/CVERecord?id=CVE-2022-48639 Référence CVE CVE-2022-48640 https://www.cve.org/CVERecord?id=CVE-2022-48640 Référence CVE CVE-2022-48641 https://www.cve.org/CVERecord?id=CVE-2022-48641 Référence CVE CVE-2022-48643 https://www.cve.org/CVERecord?id=CVE-2022-48643 Référence CVE CVE-2022-48644 https://www.cve.org/CVERecord?id=C

Official advisory

CERT-FR · French · CERTFR-2025-AVI-1054Multiples vulnérabilités dans les produits VMware

.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-2068 https://www.cve.org/CVERecord?id=CVE-2022-2068 Référence CVE CVE-2022-2097 https://www.cve.org/CVERecord?id=CVE-2022-2097 Référence CVE CVE-2022-3358 https://www.cve.org/CVERecord?id=CVE-2022-3358 Référence CVE CVE-2022-3602 https://www.cve.org/CVERecord?id=CVE-2022-3602 Référence CVE CVE-2022-3786 https://www.cve.org/CVERecord?id=CVE-2022-3786 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-48703 https://www.cve.org/CVERecord?id=CVE-2022-48703 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-0464 Référence CVE CVE-2023-0465 https://www.cve.org/CVERecord?id=CVE-2023-0465

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2022-43249 Référence CVE CVE-2022-43250 https://www.cve.org/CVERecord?id=CVE-2022-43250 Référence CVE CVE-2022-43252 https://www.cve.org/CVERecord?id=CVE-2022-43252 Référence CVE CVE-2022-43253 https://www.cve.org/CVERecord?id=CVE-2022-43253 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43680 https://www.cve.org/CVERecord?id=CVE-2022-43680 Référence CVE CVE-2022-4415 https://www.cve.org/CVERecord?id=CVE-2022-4415 Référence CVE CVE-2022-44267 https://www.cve.org/CVERecord?id=CVE-2022-44267 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-44638 https://www.cve.org/CVERecord?id=CVE-2022-44638 Référence CVE CVE-2022-45061 https://www.cve.org/CVERecord?id=CVE-2022-45061 Référence CVE CVE-2022-45873 https://www.cve.org/CVERecord?id=CVE-2022-45873 Référence CVE CVE-2022-4645 https://www.cve.org/CVERecord?id=CVE-2022-4645 Référence CVE CVE-2022-46908 https://www.cve.org/CVERecord?id=CVE-2022-46908 Référence CVE CVE-2022-48281 https://www.cve.org/CVERecord?id=CVE-2022-48281 Référence CVE CVE-2022-48303 https://www.cve.org/CVERecord?id=CVE-2022-48303 Référence CVE CVE-2022-48522 https://www.cve.org/CVERecord?id=CVE

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0967Multiples vulnérabilités dans les produits VMware

org/CVERecord?id=CVE-2022-21628 Référence CVE CVE-2022-29526 https://www.cve.org/CVERecord?id=CVE-2022-29526 Référence CVE CVE-2022-3358 https://www.cve.org/CVERecord?id=CVE-2022-3358 Référence CVE CVE-2022-3602 https://www.cve.org/CVERecord?id=CVE-2022-3602 Référence CVE CVE-2022-3786 https://www.cve.org/CVERecord?id=CVE-2022-3786 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-21830 https://www.cve.org/CVERecord?id=CVE-2023-21830 Référence CVE CVE-2023-21843 https://www.cve.org/CVERecord?id=CVE-2023-21843 Référence CVE CVE-2023-21930 https://www.cve.org/CVERecord?id=CVE-2023-21

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0864Multiples vulnérabilités dans VMware Tanzu

ve.org/CVERecord?id=CVE-2022-2068 Référence CVE CVE-2022-2097 https://www.cve.org/CVERecord?id=CVE-2022-2097 Référence CVE CVE-2022-3358 https://www.cve.org/CVERecord?id=CVE-2022-3358 Référence CVE CVE-2022-3602 https://www.cve.org/CVERecord?id=CVE-2022-3602 Référence CVE CVE-2022-3786 https://www.cve.org/CVERecord?id=CVE-2022-3786 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-40735 https://www.cve.org/CVERecord?id=CVE-2022-40735 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-45061 https://www.cve.org/CVERecord?id=CVE-2022-45061 Référence CVE CVE-2022-48560 https://www.cve.org/CVERecord?id=CVE-2022-48560 Référence CVE CVE-2022-48564 https://www.cve.org/CVERecord?id=CVE-2022-48564 Référence CVE CVE-2022-48565 https://www.cve.org/CVERecord?id=CVE-2022-48565 Référence CVE CVE-2022-48566 https://www.cve.org/CVERecord?id=CVE-2022-48566 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-20

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0756Multiples vulnérabilités dans les produits VMware

Record?id=CVE-2022-3786 Référence CVE CVE-2022-39046 https://www.cve.org/CVERecord?id=CVE-2022-39046 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-40303 https://www.cve.org/CVERecord?id=CVE-2022-40303 Référence CVE CVE-2022-40304 https://www.cve.org/CVERecord?id=CVE-2022-40304 Référence CVE CVE-2022-42010 https://www.cve.org/CVERecord?id=CVE-2022-42010 Référence CVE CVE-2022-42011 https://www.cve.org/CVERecord?id=CVE-2022-42011 Référence CVE CVE-2022-42012 https://www.cve.org/CVERecord?id=CVE-2022-42012 Référence CVE CVE-2022-4415 https://www.cve.org/CVERecord?id=CVE-2022-4415 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-44638 https://www.cve.org/CVERecord?id=CVE-2022-44638 Référence CVE CVE-2022-46908 https://www.cve.org/CVERecord?id=CVE-2022-46908 Référence CVE CVE-2022-48303 https://www.cve.org/CVERecord?id=CVE-2022-48303 Référence CVE CVE-2022-48522 https://www.cve.org/CVERecord?id=CVE-2022-48522 Référence CVE CVE-2022-48893 https://www.cve.org/CVERecord?id=CVE-2022-48893 Référence CVE CVE-2022-4899 https://www.cve.org/CVERecord?id=CVE-2022-4899 Référence CVE CVE-2022-49043 https://www.cve.org/CVERecord?id=CVE-2022-49043 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0622Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2022-41723 Référence CVE CVE-2022-41724 https://www.cve.org/CVERecord?id=CVE-2022-41724 Référence CVE CVE-2022-41725 https://www.cve.org/CVERecord?id=CVE-2022-41725 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-49636 https://www.cve.org/CVERecord?id=CVE-2022-49636 Référence CVE CVE-2022-49728 https://www.cve.org/CVERecord?id=CVE-2022-49728 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-046

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0113Multiples vulnérabilités dans les produits Siemens

VERecord?id=CVE-2022-2588 Référence CVE CVE-2022-2663 https://www.cve.org/CVERecord?id=CVE-2022-2663 Référence CVE CVE-2022-3524 https://www.cve.org/CVERecord?id=CVE-2022-3524 Référence CVE CVE-2022-39188 https://www.cve.org/CVERecord?id=CVE-2022-39188 Référence CVE CVE-2022-39842 https://www.cve.org/CVERecord?id=CVE-2022-39842 Référence CVE CVE-2022-40303 https://www.cve.org/CVERecord?id=CVE-2022-40303 Référence CVE CVE-2022-40304 https://www.cve.org/CVERecord?id=CVE-2022-40304 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43750 https://www.cve.org/CVERecord?id=CVE-2022-43750 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-47069 https://www.cve.org/CVERecord?id=CVE-2022-47069 Référence CVE CVE-2022-47929 https://www.cve.org/CVERecord?id=CVE-2022-47929 Référence CVE CVE-2023-0045 https://www.cve.org/CVERecord?id=CVE-2023-0045 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-0464 Référence CVE CVE-2023-0465 https://www.cve.org/CVERecord?id=CVE-2023-0465 Référence CVE CVE-2023-0466 https://www.cve.org/CVERecord?id=CVE-2023-046

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0781Multiples vulnérabilités dans les produits Juniper Networks

ecord?id=CVE-2021-25746 Référence CVE CVE-2021-25748 https://www.cve.org/CVERecord?id=CVE-2021-25748 Référence CVE CVE-2021-44225 https://www.cve.org/CVERecord?id=CVE-2021-44225 Référence CVE CVE-2022-23471 https://www.cve.org/CVERecord?id=CVE-2022-23471 Référence CVE CVE-2022-23524 https://www.cve.org/CVERecord?id=CVE-2022-23524 Référence CVE CVE-2022-23525 https://www.cve.org/CVERecord?id=CVE-2022-23525 Référence CVE CVE-2022-23526 https://www.cve.org/CVERecord?id=CVE-2022-23526 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-4886 https://www.cve.org/CVERecord?id=CVE-2022-4886 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-0464 Référence CVE CVE-2023-0465 https://www.cve.org/CVERecord?id=CVE-2023-0465 Ré

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0478Multiples vulnérabilités dans les produits Siemens

cord?id=CVE-2022-3643 Référence CVE CVE-2022-39189 https://www.cve.org/CVERecord?id=CVE-2022-39189 Référence CVE CVE-2022-40225 https://www.cve.org/CVERecord?id=CVE-2022-40225 Référence CVE CVE-2022-40303 https://www.cve.org/CVERecord?id=CVE-2022-40303 Référence CVE CVE-2022-40304 https://www.cve.org/CVERecord?id=CVE-2022-40304 Référence CVE CVE-2022-41742 https://www.cve.org/CVERecord?id=CVE-2022-41742 Référence CVE CVE-2022-42328 https://www.cve.org/CVERecord?id=CVE-2022-42328 Référence CVE CVE-2022-42329 https://www.cve.org/CVERecord?id=CVE-2022-42329 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-44792 https://www.cve.org/CVERecord?id=CVE-2022-44792 Référence CVE CVE-2022-44793 https://www.cve.org/CVERecord?id=CVE-2022-44793 Référence CVE CVE-2022-45886 https://www.cve.org/CVERecord?id=CVE-2022-45886 Référence CVE CVE-2022-45887 https://www.cve.org/CVERecord?id=CVE-2022-45887 Référence CVE CVE-2022-45919 https://www.cve.org/CVERecord?id=CVE-2022-45919 Référence CVE CVE-2022-46144 https://www.cve.org/CVERecord?id=CVE-2022-46144 Référence CVE CVE-2023-0160 https://www.cve.org/CVERecord?id=CVE-2023-0160 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0297Multiples vulnérabilités dans Juniper

ERecord?id=CVE-2021-37600 Référence CVE CVE-2021-39531 https://www.cve.org/CVERecord?id=CVE-2021-39531 Référence CVE CVE-2021-39533 https://www.cve.org/CVERecord?id=CVE-2021-39533 Référence CVE CVE-2021-39534 https://www.cve.org/CVERecord?id=CVE-2021-39534 Référence CVE CVE-2021-40528 https://www.cve.org/CVERecord?id=CVE-2021-40528 Référence CVE CVE-2021-41039 https://www.cve.org/CVERecord?id=CVE-2021-41039 Référence CVE CVE-2022-2795 https://www.cve.org/CVERecord?id=CVE-2022-2795 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-48522 https://www.cve.org/CVERecord?id=CVE-2022-48522 Référence CVE CVE-2022-48554 https://www.cve.org/CVERecord?id=CVE-2022-48554 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-0466 https://www.cve.org/CVERecord?id=CVE-2023-046

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0237Multiples vulnérabilités dans les produits Belden

De multiples vulnérabilités ont été découvertes dans Belden. Elles permettent à un attaquant de provoquer un déni de service à distance, un contournement de la politique de sécurité et une atteinte à la confidentialité des données.

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0180Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2022-21496 Référence CVE CVE-2022-34165 https://www.cve.org/CVERecord?id=CVE-2022-34165 Référence CVE CVE-2022-34169 https://www.cve.org/CVERecord?id=CVE-2022-34169 Référence CVE CVE-2022-34357 https://www.cve.org/CVERecord?id=CVE-2022-34357 Référence CVE CVE-2022-40609 https://www.cve.org/CVERecord?id=CVE-2022-40609 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-41854 https://www.cve.org/CVERecord?id=CVE-2022-41854 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-46364 https://www.cve.org/CVERecord?id=CVE-2022-46364 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-0464 Référence CVE CVE-2023-0465 https://www.cve.org/CVERecord?id=CVE-2023-0465

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0145Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2022-41715 Référence CVE CVE-2022-41716 https://www.cve.org/CVERecord?id=CVE-2022-41716 Référence CVE CVE-2022-41717 https://www.cve.org/CVERecord?id=CVE-2022-41717 Référence CVE CVE-2022-41723 https://www.cve.org/CVERecord?id=CVE-2022-41723 Référence CVE CVE-2022-41724 https://www.cve.org/CVERecord?id=CVE-2022-41724 Référence CVE CVE-2022-41725 https://www.cve.org/CVERecord?id=CVE-2022-41725 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43548 https://www.cve.org/CVERecord?id=CVE-2022-43548 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-48337 https://www.cve.org/CVERecord?id=CVE-2022-48337 Référence CVE CVE-2022-48339 https://www.cve.org/CVERecord?id=CVE-2022-48339 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-0464 Référence CVE CVE-2023-0465 https://www.cve.org/CVERecord?id=CVE-2023-0465 Référence CVE CVE-2023-0466 https://www.cve.org/CVERecord?id=CVE-2023-0466 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-137

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0119Multiples vulnérabilités dans les produits Siemens

ERecord?id=CVE-2022-41860 Référence CVE CVE-2022-41861 https://www.cve.org/CVERecord?id=CVE-2022-41861 Référence CVE CVE-2022-41862 https://www.cve.org/CVERecord?id=CVE-2022-41862 Référence CVE CVE-2022-41903 https://www.cve.org/CVERecord?id=CVE-2022-41903 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-42919 https://www.cve.org/CVERecord?id=CVE-2022-42919 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4415 https://www.cve.org/CVERecord?id=CVE-2022-4415 Référence CVE CVE-2022-44370 https://www.cve.org/CVERecord?id=CVE-2022-44370 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-45061 https://www.cve.org/CVERecord?id=CVE-2022-45061 Référence CVE CVE-2022-45142 https://www.cve.org/CVERecord?id=CVE-2022-45142 Référence CVE CVE-2022-45919 https://www.cve.org/CVERecord?id=CVE-2022-45919 Référence CVE CVE-2022-46392 https://www.cve.org/CVERecord?id=CVE-2022-46392 Référence CVE CVE-2022-46393 https://www.cve.org/CVERecord?id=CVE-2022-46393 Référence CVE CVE-2022-4743 https://www.cve.org/CVERecord?id=CVE-2022-4743 Référence CVE CVE-2022-4744 https://www.cve.org/CVERecord?id=CVE-2022-4744 Référence CVE CVE-2022-47629 https://www.cve.org/CVERecord?id=CVE-2

Official advisory

CERT-FR · French · CERTFR-2023-AVI-1015Multiples vulnérabilités dans les produits Siemens

ord?id=CVE-2022-40674 Référence CVE CVE-2022-42784 https://www.cve.org/CVERecord?id=CVE-2022-42784 Référence CVE CVE-2022-42898 https://www.cve.org/CVERecord?id=CVE-2022-42898 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43680 https://www.cve.org/CVERecord?id=CVE-2022-43680 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-45061 https://www.cve.org/CVERecord?id=CVE-2022-45061 Référence CVE CVE-2022-45873 https://www.cve.org/CVERecord?id=CVE-2022-45873 Référence CVE CVE-2022-46141 https://www.cve.org/CVERecord?id=CVE-2022-46141 Référence CVE CVE-2022-46143 https://www.cve.org/CVERecord?id=CVE-2022-46143 Référence CVE CVE-2022-46908 https://www.cve.org/CVERecord?id=CVE-2022-46908 Référence CVE CVE-2022-47374 https://www.cve.org/CVERecord?id=CVE-2022-47374 Référence CVE CVE-2022-47375 https://www.cve.org/CVERecord?id=CVE-2022-47375 Référence CVE CVE-2022-48303 https://www.cve.org/CVERecord?id=C

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0935Multiples vulnérabilités dans les produits Siemens

ecord?id=CVE-2022-28807 Référence CVE CVE-2022-28808 https://www.cve.org/CVERecord?id=CVE-2022-28808 Référence CVE CVE-2022-28809 https://www.cve.org/CVERecord?id=CVE-2022-28809 Référence CVE CVE-2022-30184 https://www.cve.org/CVERecord?id=CVE-2022-30184 Référence CVE CVE-2022-37434 https://www.cve.org/CVERecord?id=CVE-2022-37434 Référence CVE CVE-2022-39158 https://www.cve.org/CVERecord?id=CVE-2022-39158 Référence CVE CVE-2022-41032 https://www.cve.org/CVERecord?id=CVE-2022-41032 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-44792 https://www.cve.org/CVERecord?id=CVE-2022-44792 Référence CVE CVE-2022-44793 https://www.cve.org/CVERecord?id=CVE-2022-44793 Référence CVE CVE-2022-47522 https://www.cve.org/CVERecord?id=CVE-2022-47522 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-0933 https://www.cve.org/CVERecord?id=CVE-2023-0933 Référence CVE CVE-2023-1530 https://www.cve.org/CVERecord?id=CVE-2023-1

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0526Multiples vulnérabilités dans les produits Siemens

ord?id=CVE-2022-27782 Référence CVE CVE-2022-29561 https://www.cve.org/CVERecord?id=CVE-2022-29561 Référence CVE CVE-2022-29562 https://www.cve.org/CVERecord?id=CVE-2022-29562 Référence CVE CVE-2022-30767 https://www.cve.org/CVERecord?id=CVE-2022-30767 Référence CVE CVE-2022-31810 https://www.cve.org/CVERecord?id=CVE-2022-31810 Référence CVE CVE-2022-32207 https://www.cve.org/CVERecord?id=CVE-2022-32207 Référence CVE CVE-2022-36946 https://www.cve.org/CVERecord?id=CVE-2022-36946 Référence CVE CVE-2022-37434 https://www.cve.org/CVERecord?id=CVE-2022-37434 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-48285 https://www.cve.org/CVERecord?id=CVE-2022-48285 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-29130 https://www.cve.org/CVERecord?id=CVE-2023-29130 Référence CVE CVE-2023-29131 https://www.cve.org/CVERecord?id=CVE-2023-29131 Référence CVE CVE-2023-35920 https://www.cve.org/CVERecord?id=CVE-2023-35920 Référence CVE CVE-2023-35921 https://www.cve.org/CVERecord?id=CVE-2023-35921 Référence CVE CVE-2023-36386 https://www.cve.org/CVERecord?id=CVE-2

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0484Multiples vulnérabilités dans les produits IBM

ERecord?id=CVE-2022-41727 Référence CVE CVE-2022-4269 https://www.cve.org/CVERecord?id=CVE-2022-4269 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-4378 https://www.cve.org/CVERecord?id=CVE-2022-4378 Référence CVE CVE-2022-43927 https://www.cve.org/CVERecord?id=CVE-2022-43927 Référence CVE CVE-2022-43929 https://www.cve.org/CVERecord?id=CVE-2022-43929 Référence CVE CVE-2022-43930 https://www.cve.org/CVERecord?id=CVE-2022-43930 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-45061 https://www.cve.org/CVERecord?id=CVE-2022-45061 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0266 https://www.cve.org/CVERecord?id=CVE-2023-0266 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0386 https://www.cve.org/CVERecord?id=CVE-2023-0386 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=CVE-2023-0464 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0453Multiples vulnérabilités dans les produits Siemens

ecord?id=CVE-2022-42895 Référence CVE CVE-2022-42896 https://www.cve.org/CVERecord?id=CVE-2022-42896 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43398 https://www.cve.org/CVERecord?id=CVE-2022-43398 Référence CVE CVE-2022-43439 https://www.cve.org/CVERecord?id=CVE-2022-43439 Référence CVE CVE-2022-43545 https://www.cve.org/CVERecord?id=CVE-2022-43545 Référence CVE CVE-2022-43546 https://www.cve.org/CVERecord?id=CVE-2022-43546 Référence CVE CVE-2022-43750 https://www.cve.org/CVERecord?id=CVE-2022-43750 Référence CVE CVE-2022-4378 https://www.cve.org/CVERecord?id=CVE-2022-4378 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-4662 https://www.cve.org/CVERecord?id=CVE-2022-4662 Référence CVE CVE-2022-47518 https://www.cve.org/CVERecord?id=CVE-2022-47518 Référence CVE CVE-2022-47520 https://www.cve.org/CVERecord?id=CVE-2022-47520 Référence CVE CVE-2022-47929 https://www.cve.org/CVERecord?id=CVE-2022-47929 Référence CVE CVE-2022-47946 https://www.cve.org/CVERecord?id=CVE-2022-47946 Référence CVE CVE-2023-0179 https://www.cve.org/CVERecord?id=CVE-2023-0179 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0444Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2022-38752 Référence CVE CVE-2022-40152 https://www.cve.org/CVERecord?id=CVE-2022-40152 Référence CVE CVE-2022-41854 https://www.cve.org/CVERecord?id=CVE-2022-41854 Référence CVE CVE-2022-41881 https://www.cve.org/CVERecord?id=CVE-2022-41881 Référence CVE CVE-2022-41915 https://www.cve.org/CVERecord?id=CVE-2022-41915 Référence CVE CVE-2022-42003 https://www.cve.org/CVERecord?id=CVE-2022-42003 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-46175 https://www.cve.org/CVERecord?id=CVE-2022-46175 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23916 Référence CVE CVE-2023-24998 https://www.cve.org/CVERecord?id=CVE-2023-24

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0368Multiples vulnérabilités dans Nessus Network Monitor

ecord?id=CVE-2022-23852 Référence CVE CVE-2022-23990 https://www.cve.org/CVERecord?id=CVE-2022-23990 Référence CVE CVE-2022-25235 https://www.cve.org/CVERecord?id=CVE-2022-25235 Référence CVE CVE-2022-25236 https://www.cve.org/CVERecord?id=CVE-2022-25236 Référence CVE CVE-2022-25314 https://www.cve.org/CVERecord?id=CVE-2022-25314 Référence CVE CVE-2022-25315 https://www.cve.org/CVERecord?id=CVE-2022-25315 Référence CVE CVE-2022-40674 https://www.cve.org/CVERecord?id=CVE-2022-40674 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Gestion détaillée du document le 10 mai 2023 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense e

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0271Multiples vulnérabilités dans les produits Qnap

De multiples vulnérabilités ont été découvertes dans les produits Qnap . Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une atteinte à la confidentialité des données et un contournement de la politique de sécurité.

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0258Multiples vulnérabilités dans les produits IBM

ERecord?id=CVE-2022-41716 Référence CVE CVE-2022-41717 https://www.cve.org/CVERecord?id=CVE-2022-41717 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4269 https://www.cve.org/CVERecord?id=CVE-2022-4269 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43548 https://www.cve.org/CVERecord?id=CVE-2022-43548 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43945 https://www.cve.org/CVERecord?id=CVE-2022-43945 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-22809 https://www.cve.org/CVERecord?id=CVE-2023-22809 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0239Multiples vulnérabilités dans Tenable Sensor Proxy

De multiples vulnérabilités ont été découvertes dans Tenable Sensor Proxy . Elles permettent à un attaquant de provoquer un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0245Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été corrigées dans les produits IBM . Certaines d'entre elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur, un déni de service à distance et une atteinte à l'intégrité des données.

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0220Multiples vulnérabilités dans les produits Siemens

ord?id=CVE-2022-32208 Référence CVE CVE-2022-32296 https://www.cve.org/CVERecord?id=CVE-2022-32296 Référence CVE CVE-2022-32981 https://www.cve.org/CVERecord?id=CVE-2022-32981 Référence CVE CVE-2022-33981 https://www.cve.org/CVERecord?id=CVE-2022-33981 Référence CVE CVE-2022-35252 https://www.cve.org/CVERecord?id=CVE-2022-35252 Référence CVE CVE-2022-36879 https://www.cve.org/CVERecord?id=CVE-2022-36879 Référence CVE CVE-2022-36946 https://www.cve.org/CVERecord?id=CVE-2022-36946 Référence CVE CVE-2022-38767 https://www.cve.org/CVERecord?id=CVE-2022-38767 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-25957 https://www.cve.org/CVERecord?id=CVE-2023-25957 Référence CVE CVE-2023-27309 https://www.cve.org/CVERecord?id=CVE-2023-27309 Référence CVE CVE-2023-27310 https://www.cve.org/CVERecord?id=CVE-2023-27310 Référence CVE CVE-2023-27462 https://www.cve.org/CVERecord?id=CVE-2023-27462 Référence CVE CVE-2023-27463 https://www.cve.org/CVERecord?id=CVE-2023-27463 Gestion détaillée du document le 14 mars 2023 Version initiale Aler

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0214Multiples vulnérabilités dans les produits IBM

VERecord?id=CVE-2021-4160 Référence CVE CVE-2021-43138 https://www.cve.org/CVERecord?id=CVE-2021-43138 Référence CVE CVE-2022-0391 https://www.cve.org/CVERecord?id=CVE-2022-0391 Référence CVE CVE-2022-24758 https://www.cve.org/CVERecord?id=CVE-2022-24758 Référence CVE CVE-2022-25881 https://www.cve.org/CVERecord?id=CVE-2022-25881 Référence CVE CVE-2022-34339 https://www.cve.org/CVERecord?id=CVE-2022-34339 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43879 https://www.cve.org/CVERecord?id=CVE-2022-43879 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23915 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0208Multiples vulnérabilités dans Nessus

De multiples vulnérabilités ont été découvertes dans les produits Tenable . Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et un contournement de la politique de sécurité.

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0198Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM . Elles permettent à un attaquant de provoquer un déni de service à distance et un contournement de la politique de sécurité.

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0201Multiples vulnérabilités dans Tenable Nessus

De multiples vulnérabilités ont été découvertes dans Tenable Nessus . Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0190Multiples vulnérabilités dans Tenable Nessus

De multiples vulnérabilités ont été découvertes dans Tenable Nessus. Certaines d'entre elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur, une exécution de code arbitraire à distance et un déni de service à distance.

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0183Multiples vulnérabilités dans Tenable.sc

De multiples vulnérabilités ont été découvertes dans Tenable.sc. Elles permettent à un attaquant de provoquer un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0153Multiples vulnérabilités dans Stormshield Network Security

De multiples vulnérabilités ont été corrigées dans Stormshield Network Security. Elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

Official advisory

CERT-FR · French · CERTFR-2023-AVI-0102Multiples vulnérabilités dans OpenSSL

De multiples vulnérabilités ont été découvertes dans OpenSSL. Elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à l'intégrité des données et une atteinte à la confidentialité des données.

Official advisory

NCSC-NL · Dutch · NCSC-2024-0246Kwetsbaarheden verholpen in Siemens producten

De kwetsbaarheden stellen een kwaadwillende mogelijk in staat aanvallen uit te voeren die kunnen leiden tot de volgende categorieën schade: - Denial-of-Service (DoS) - Manipulatie van gegevens - Omzeilen van beveiligingsmaatregel - (Remote) code execution (Administrator/Root rechten) - (Remote) code execution (Gebruikersrechten) - Toegang tot systeemgegevens - Verhoogde gebruikersrechten De kwaadwillende heeft hiervoor toegang nodig tot de productieomgeving. Het is goed gebruik een dergelijke omgeving niet publiek toegankelijk te hebben.

Official advisory

NCSC-NL · Dutch · NCSC-2025-0061Kwetsbaarheden verholpen in Siemens producten

De kwetsbaarheden stellen een kwaadwillende mogelijk in staat aanvallen uit te voeren die kunnen leiden tot de volgende categorieën schade: - Denial-of-Service (DoS) - Cross-Site-Scripting (XSS) - Cross-Site Request Forgery (CSRF) - Manipulatie van gegevens - Omzeilen van een beveiligingsmaatregel - Omzeilen van authenticatie - (Remote) code execution (root/admin rechten) - (Remote) code execution (Gebruikersrechten) - Toegang tot systeemgegevens - Toegang tot gevoelige gegevens De kwaadwillende heeft hiervoor toegang nodig tot de productieomgeving. Het is goed gebruik een dergelijke omgeving niet publiek toegankelijk te hebben.

Official advisory

NCSC-NL · Dutch · NCSC-2025-0051Kwetsbaarheden verholpen in Siemens producten

De kwetsbaarheden stellen een kwaadwillende mogelijk in staat aanvallen uit te voeren die kunnen leiden tot de volgende categorieën schade: - Denial-of-Service (DoS) - Cross-Site-Scripting (XSS) - Cross-Site Request Forgery (CSRF) - Manipulatie van gegevens - Omzeilen van een beveiligingsmaatregel - Omzeilen van authenticatie - (Remote) code execution (root/admin rechten) - (Remote) code execution (Gebruikersrechten) - Toegang tot systeemgegevens - Toegang tot gevoelige gegevens De kwaadwillende heeft hiervoor toegang nodig tot de productieomgeving. Het is goed gebruik een dergelijke omgeving niet publiek toegankelijk te hebben.

Official advisory

03

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0); SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0); SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0); SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0); SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Update to V3.1.5 or later version
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

04

Evidence and provenance

Published 8 Feb 2023 · Last source change 4 Nov 2025, 19:14 UTC · CWE-415 · Double Free

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

?

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2023-0796

Product sourceVendor CSAF · Siemens ProductCERT

Remediation sourceVendor CSAF · Siemens ProductCERT

CWE sourceCISA ADP

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2023-02-08CVE published

2025-11-04Fixed release or patch reference recorded

ENISA EUVD · EUVD-2023-0796↗Vendor CSAF · Siemens ProductCERT↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.