BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2023
CVE-2023-0361High confidence

This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack

Unknown · gnutls

Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.

7.4HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 19 Mar 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.42% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown gnutls and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · maingnutlsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.8.0-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · maingnutlsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.8.0-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · maingnutlsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.8.0-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcegnutls28Vendor fix publishedDebian records a fixed source-package version for this release.3.7.8-5Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcegnutls28Vendor fix publishedDebian records a fixed source-package version for this release.3.7.8-5Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegnutls28Vendor fix publishedDebian records a fixed source-package version for this release.3.7.8-5Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegnutls28Vendor fix publishedDebian records a fixed source-package version for this release.3.7.8-5Debian Security Tracker ↗Source updated 5 Oct 2026
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.

2 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
A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.
Remediation
Update to V3.1.5 or later version
SSA-806742 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-806742: Multiple Vulnerabilities in SCALANCE XCM-/XRM-300 before V2.4
11 known affected

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

  • SCALANCE XCH328 (6GK5328-4TS01-2EC2)
  • SCALANCE XCM324 (6GK5324-8TS01-2AC2)
  • SCALANCE XCM328 (6GK5328-4TS01-2AC2)
  • SCALANCE XCM332 (6GK5332-0GA01-2AC2)
  • SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)
  • SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)
  • SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)
  • SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)
  • SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)
  • SCALANCE XRM334 (2x230 V AC, 12xFO) (6GK5334-3TS01-4AR3)
  • SCALANCE XRM334 (2x230 V AC, 8xFO) (6GK5334-2TS01-4AR3)
Summary
A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.
Remediation
Update to V2.4 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-12422

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 actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.

What

A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.

Why

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.

Why

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Observable Discrepancy → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
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-203 ↗

CWE-203: Observable Discrepancy. The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.

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:H/PR:N/UI:N/S:U/C:H/I:H/A:N

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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
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.
NetworkUnauthenticatedCWE-203Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2023-2679Oracle 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-2023-1794Oracle MySQL: Mehrere Schwachstellen

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

Official advisory ↗
BSI · German · WID-SEC-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-2023-1542Red Hat OpenShift: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um einen Denial of Service Zustand herbeizuführen, Informationen offenzulegen, Dateien zu manipulieren oder Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2023-1021Oracle 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-2023-0353GnuTLS: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in GnuTLS ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20230222Security Bulletin 22 Feb 2023

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Feb 2023, published on 22 February 2023. Open the linked bulletin for the product, severity and reference information published in that issue.

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

g/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-2022-48703 https://www.cve.org/CVERecord?id=CVE-2022-48703 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-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-0361 https://www.cve.org/CVERecord?id=CVE-2023-0361 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éférence CVE CVE-2023-0466 https://www.cve.org/CVERecord?id=CVE-2023-0466 Référence CVE CVE-2023-0614 https://www.cve.org/CVERecord?id=CVE-2023-0614 Référence CVE CVE-2023-0687 https://www.cve.org/CVERecord?id=CVE-2023-0687 Référence CVE CVE-2023-0767 https://www.cve.org/CVERecord?id=CVE-2023-0767 Référence CVE CVE-2023-0795 https://www.cve.org/CVERecord?id=CVE-2023-0795 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0630Multiples vulnérabilités dans IBM QRadar

cord?id=CVE-2021-3757 Référence CVE CVE-2021-42740 https://www.cve.org/CVERecord?id=CVE-2021-42740 Référence CVE CVE-2021-43138 https://www.cve.org/CVERecord?id=CVE-2021-43138 Référence CVE CVE-2022-25881 https://www.cve.org/CVERecord?id=CVE-2022-25881 Référence CVE CVE-2022-25883 https://www.cve.org/CVERecord?id=CVE-2022-25883 Référence CVE CVE-2022-3517 https://www.cve.org/CVERecord?id=CVE-2022-3517 Référence CVE CVE-2022-37601 https://www.cve.org/CVERecord?id=CVE-2022-37601 Référence CVE CVE-2022-37603 https://www.cve.org/CVERecord?id=CVE-2022-37603 Référence CVE CVE-2022-43441 https://www.cve.org/CVERecord?id=CVE-2022-43441 Référence CVE CVE-2023-0361 https://www.cve.org/CVERecord?id=CVE-2023-0361 Référence CVE CVE-2023-0842 https://www.cve.org/CVERecord?id=CVE-2023-0842 Référence CVE CVE-2023-32233 https://www.cve.org/CVERecord?id=CVE-2023-32233 Référence CVE CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 Référence CVE CVE-2023-3446 https://www.cve.org/CVERecord?id=CVE-2023-3446 Référence CVE CVE-2023-35001 https://www.cve.org/CVERecord?id=CVE-2023-35001 Référence CVE CVE-2023-3609 https://www.cve.org/CVERecord?id=CVE-2023-3609 Référence CVE CVE-2023-36632 https://www.cve.org/CVERecord?id=CVE-2023-36632 Référence CVE CVE-2023-3817 https://www.cve.org/CVERecord?id=CVE-2023-3

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

cve.org/CVERecord?id=CVE-2022-48434 Référence CVE CVE-2022-4900 https://www.cve.org/CVERecord?id=CVE-2022-4900 Référence CVE CVE-2022-4904 https://www.cve.org/CVERecord?id=CVE-2022-4904 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-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-0330 https://www.cve.org/CVERecord?id=CVE-2023-0330 Référence CVE CVE-2023-0361 https://www.cve.org/CVERecord?id=CVE-2023-0361 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-0401 Référence CVE CVE-2023-0494 https://www.cve.org/CVERecord?id=CVE-2023-0494 Référence CVE CVE-2023-0567 https://www.cve.org/CVERecord?id=CVE-2023-0567 Référence CVE CVE-2023-0568 https://www.cve.org/CVERecord?id=CVE-2023-0568 Référence CVE CVE-2023-0590 https://www.cve.org/CVERecord?id=CVE-2023-0590 Référence CVE CVE-2023-0662 https://www.cve.org/CVERecord?id=CVE-2023-0662 Référence CVE CVE-2023-1206 https://www.cve.org/CVERecord?id=CVE-2023-1206 Référence CVE CVE-2023-1255 https://www.cve.org/CVERecord?id=CVE-2023-1255 Ré

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

ecord?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=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-48560 https://www.cve.org/CVERecord?id=CVE-2022-48560 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-0361 https://www.cve.org/CVERecord?id=CVE-2023-0361 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-0687 https://www.cve.org/CVERecord?id=CVE-2023-0687 Référence CVE CVE-2023-1077 https://www.cve.org/CVERecord?id=CVE-2023-1077 Référence CVE CVE-2023-1206 https://www.cve.org/CVERecord?id=CVE-2023-1206 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-2391

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0563Multiples vulnérabilités dans Oracle MySQL

on de code arbitraire à distance, un déni de service à distance et une atteinte à l'intégrité des données. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Oracle cpujul2023 du 18 juillet 2023 https://www.oracle.com/security-alerts/cpujul2023.html Bulletin de sécurité Oracle cpujul2023verbose du 18 juillet 2023 https://www.oracle.com/security-alerts/cpujul2023verbose.html#MSQL Référence CVE CVE-2022-37865 https://www.cve.org/CVERecord?id=CVE-2022-37865 Référence CVE CVE-2022-4899 https://www.cve.org/CVERecord?id=CVE-2022-4899 Référence CVE CVE-2023-0361 https://www.cve.org/CVERecord?id=CVE-2023-0361 Référence CVE CVE-2023-20862 https://www.cve.org/CVERecord?id=CVE-2023-20862 Référence CVE CVE-2023-21950 https://www.cve.org/CVERecord?id=CVE-2023-21950 Référence CVE CVE-2023-22005 https://www.cve.org/CVERecord?id=CVE-2023-22005 Référence CVE CVE-2023-22007 https://www.cve.org/CVERecord?id=CVE-2023-22007 Référence CVE CVE-2023-22008 https://www.cve.org/CVERecord?id=CVE-2023-22008 Référence CVE CVE-2023-22033 https://www.cve.org/CVERecord?id=CVE-2023-22033 Référence CVE CVE-2023-22038 https://www.cve.org/CVERecord?id=CVE-2023-22038 Référence CVE CVE-2023-22046 https://www.cve.org/CVERecord?id=C

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-004167GNU Project の GnuTLS 他複数ベンダの製品における観測可能な不一致に関する脆弱性

GNU Project の GnuTLS 他複数ベンダの製品には、観測可能な不一致に関する脆弱性が存在します。

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.
Fix availability varies by product
Affected
Fixed
Update to V3.1.5 or later version
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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 15 Feb 2023 · Last source change 19 Mar 2025, 17:45 UTC · CWE-203 · Observable Discrepancy

CVE recordCVE.org · 5.1
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-12422
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    gnutls-3.7.6 · 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.
    After
    gnutls-3.7.6 · Fixed: Update to V3.1.5 or later version
    Siemens ProductCERT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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.
Free version - for non-commercial use only.CVE-2023-0361 · cve.blacktree.nl