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

Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channel

Go standard library · crypto/tls

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.25% 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.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Go standard library crypto/tls 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 30 daysRemediation target: Within 180 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 2 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

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

1 package state
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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
Debian bookwormbookworm · sourcegolang-1.19Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian 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.

1 current
CVE-2023-45287 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygolang: crypto/tls: Timing Side Channel attack in RSA based TLS key exchanges.
72 known affected

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

  • cryostat-tech-preview/cryostat-rhel8-operator as a component of Cryostat 2
  • lvms4/topolvm-rhel8 as a component of Logical Volume Manager Storage
  • mta/mta-hub-rhel9 as a component of Migration Toolkit for Applications 6
  • migration-toolkit-virtualization/mtv-api-rhel9 as a component of Migration Toolkit for Virtualization
  • mirror-registry-container as a component of mirror registry for Red Hat OpenShift
  • tang-operator-container as a component of NBDE Tang Server
  • helm.src as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services
  • openshift-pipelines-client.src as a component of OpenShift Pipelines
  • kepler-container as a component of Power monitoring for Red Hat OpenShift
  • 3scale-operator-container as a component of Red Hat 3scale API Management Platform 2
  • rhacm2/subctl-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2
Summary
A flaw was found in the Golang crypto/tls standard library. In previous versions, the package was vulnerable to a Timing Side Channel attack by observing the time it took for RSA-based TLS key exchanges, which was not constant. This flaw allows a malicious user to gather information from the environment.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
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-49587

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; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 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

Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

What

Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

Why

Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.

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

Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

Why

Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.

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.
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 → Observable Timing 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
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-208 ↗

CWE-208: Observable Timing Discrepancy. Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.

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:H/I:N/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.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.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.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-208
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-1226Red Hat OpenShift: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Dateien zu manipulieren, einen Denial-of-Service-Zustand zu verursachen, beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder um weitere nicht spezifizierte Angriffe auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0521IBM MQ: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM MQ ausnutzen, um beliebigen Programmcode auszuführen, Informationen offenzulegen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-1228Red Hat OpenStack: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenStack ausnutzen, um Sicherheitsmaßnahmen zu umgehen, eine Denial-of-Service-Zustand zu erzeugen, um vertrauliche Informationen offenzulegen und Daten zu ändern.

Official advisory ↗
BSI · German · WID-SEC-2023-3059Golang Go: Schwachstelle ermöglicht Offenlegung von Informationen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Golang Go ausnutzen, um Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20231206Security Bulletin 06 Dec 2023

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

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

d?id=CVE-2023-29409 Référence CVE CVE-2023-39318 https://www.cve.org/CVERecord?id=CVE-2023-39318 Référence CVE CVE-2023-39319 https://www.cve.org/CVERecord?id=CVE-2023-39319 Référence CVE CVE-2023-39323 https://www.cve.org/CVERecord?id=CVE-2023-39323 Référence CVE CVE-2023-39326 https://www.cve.org/CVERecord?id=CVE-2023-39326 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Référence CVE CVE-2023-45283 https://www.cve.org/CVERecord?id=CVE-2023-45283 Référence CVE CVE-2023-45284 https://www.cve.org/CVERecord?id=CVE-2023-45284 Référence CVE CVE-2023-45285 https://www.cve.org/CVERecord?id=CVE-2023-45285 Référence CVE CVE-2023-45287 https://www.cve.org/CVERecord?id=CVE-2023-45287 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-45289 https://www.cve.org/CVERecord?id=CVE-2023-45289 Référence CVE CVE-2023-45290 https://www.cve.org/CVERecord?id=CVE-2023-45290 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2024-24783 https://www.cve.org/CVERecord?id=CVE-2024-24783 Référence CVE CVE-2024-24784 https://www.cve.org/CVERecord?id=CVE-2024-24784 Référence CVE CVE-2024-24785 https://www.cve.org/CVERecord?id=CVE-2024-24785 Référence CVE CVE-2024-24786 https://www.cve.org/CVERecord?id=

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

rd?id=CVE-2023-3978 Référence CVE CVE-2023-42363 https://www.cve.org/CVERecord?id=CVE-2023-42363 Référence CVE CVE-2023-42364 https://www.cve.org/CVERecord?id=CVE-2023-42364 Référence CVE CVE-2023-42365 https://www.cve.org/CVERecord?id=CVE-2023-42365 Référence CVE CVE-2023-42366 https://www.cve.org/CVERecord?id=CVE-2023-42366 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Référence CVE CVE-2023-45283 https://www.cve.org/CVERecord?id=CVE-2023-45283 Référence CVE CVE-2023-45284 https://www.cve.org/CVERecord?id=CVE-2023-45284 Référence CVE CVE-2023-45285 https://www.cve.org/CVERecord?id=CVE-2023-45285 Référence CVE CVE-2023-45287 https://www.cve.org/CVERecord?id=CVE-2023-45287 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-45289 https://www.cve.org/CVERecord?id=CVE-2023-45289 Référence CVE CVE-2023-45290 https://www.cve.org/CVERecord?id=CVE-2023-45290 Référence CVE CVE-2023-46218 https://www.cve.org/CVERecord?id=CVE-2023-46218 Référence CVE CVE-2023-47090 https://www.cve.org/CVERecord?id=CVE-2023-47090 Référence CVE CVE-2023-4807 https://www.cve.org/CVERecord?id=CVE-2023-4807 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2023-5363 https://www.cve.org/CVERecord?id=CVE

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

CVERecord?id=CVE-2022-31197 Référence CVE CVE-2022-3171 https://www.cve.org/CVERecord?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-41946 https://www.cve.org/CVERecord?id=CVE-2022-41946 Référence CVE CVE-2022-49985 https://www.cve.org/CVERecord?id=CVE-2022-49985 Référence CVE CVE-2022-50087 https://www.cve.org/CVERecord?id=CVE-2022-50087 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-1370 Référence CVE CVE-2023-26133 https://www.cve.org/CVERecord?id=CVE-2023-26133 Référence CVE CVE-2023-45287 https://www.cve.org/CVERecord?id=CVE-2023-45287 Référence CVE CVE-2023-46308 https://www.cve.org/CVERecord?id=CVE-2023-46308 Référence CVE CVE-2023-53125 https://www.cve.org/CVERecord?id=CVE-2023-53125 Référence CVE CVE-2023-53373 https://www.cve.org/CVERecord?id=CVE-2023-53373 Référence CVE CVE-2024-1597 https://www.cve.org/CVERecord?id=CVE-2024-1597 Référence CVE CVE-2024-35255 https://www.cve.org/CVERecord?id=CVE-2024-35255 Référence CVE CVE-2024-47252 https://www.cve.org/CVERecord?id=CVE-2024-47252 Référence CVE CVE-2024-47619 https://www.cve.org/CVERecord?id=CVE-2024-47619 Référence CVE CVE-2024-49350 https://www.cve.org/CVERecord?id=CV

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

cord?id=CVE-2023-4154 Référence CVE CVE-2023-42669 https://www.cve.org/CVERecord?id=CVE-2023-42669 Référence CVE CVE-2023-42670 https://www.cve.org/CVERecord?id=CVE-2023-42670 Référence CVE CVE-2023-43887 https://www.cve.org/CVERecord?id=CVE-2023-43887 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Référence CVE CVE-2023-4527 https://www.cve.org/CVERecord?id=CVE-2023-4527 Référence CVE CVE-2023-45283 https://www.cve.org/CVERecord?id=CVE-2023-45283 Référence CVE CVE-2023-45284 https://www.cve.org/CVERecord?id=CVE-2023-45284 Référence CVE CVE-2023-45285 https://www.cve.org/CVERecord?id=CVE-2023-45285 Référence CVE CVE-2023-45287 https://www.cve.org/CVERecord?id=CVE-2023-45287 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-45289 https://www.cve.org/CVERecord?id=CVE-2023-45289 Référence CVE CVE-2023-45290 https://www.cve.org/CVERecord?id=CVE-2023-45290 Référence CVE CVE-2023-45322 https://www.cve.org/CVERecord?id=CVE-2023-45322 Référence CVE CVE-2023-45853 https://www.cve.org/CVERecord?id=CVE-2023-45853 Référence CVE CVE-2023-45913 https://www.cve.org/CVERecord?id=CVE-2023-45913 Référence CVE CVE-2023-45919 https://www.cve.org/CVERecord?id=CVE-2023-45919 Référence CVE CVE-2023-45922 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2023-39325 Référence CVE CVE-2023-39326 https://www.cve.org/CVERecord?id=CVE-2023-39326 Référence CVE CVE-2023-3978 https://www.cve.org/CVERecord?id=CVE-2023-3978 Référence CVE CVE-2023-40217 https://www.cve.org/CVERecord?id=CVE-2023-40217 Référence CVE CVE-2023-40403 https://www.cve.org/CVERecord?id=CVE-2023-40403 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Référence CVE CVE-2023-45283 https://www.cve.org/CVERecord?id=CVE-2023-45283 Référence CVE CVE-2023-45284 https://www.cve.org/CVERecord?id=CVE-2023-45284 Référence CVE CVE-2023-45285 https://www.cve.org/CVERecord?id=CVE-2023-45285 Référence CVE CVE-2023-45287 https://www.cve.org/CVERecord?id=CVE-2023-45287 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-45289 https://www.cve.org/CVERecord?id=CVE-2023-45289 Référence CVE CVE-2023-45290 https://www.cve.org/CVERecord?id=CVE-2023-45290 Référence CVE CVE-2023-46218 https://www.cve.org/CVERecord?id=CVE-2023-46218 Référence CVE CVE-2023-46737 https://www.cve.org/CVERecord?id=CVE-2023-46737 Référence CVE CVE-2023-4807 https://www.cve.org/CVERecord?id=CVE-2023-4807 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0524Multiples vulnérabilités dans VMware Tanzu

ecord?id=CVE-2023-39319 Référence CVE CVE-2023-39323 https://www.cve.org/CVERecord?id=CVE-2023-39323 Référence CVE CVE-2023-39326 https://www.cve.org/CVERecord?id=CVE-2023-39326 Référence CVE CVE-2023-39328 https://www.cve.org/CVERecord?id=CVE-2023-39328 Référence CVE CVE-2023-39329 https://www.cve.org/CVERecord?id=CVE-2023-39329 Référence CVE CVE-2023-4016 https://www.cve.org/CVERecord?id=CVE-2023-4016 Référence CVE CVE-2023-4039 https://www.cve.org/CVERecord?id=CVE-2023-4039 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Référence CVE CVE-2023-45285 https://www.cve.org/CVERecord?id=CVE-2023-45285 Référence CVE CVE-2023-45287 https://www.cve.org/CVERecord?id=CVE-2023-45287 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-45289 https://www.cve.org/CVERecord?id=CVE-2023-45289 Référence CVE CVE-2023-45290 https://www.cve.org/CVERecord?id=CVE-2023-45290 Référence CVE CVE-2023-45853 https://www.cve.org/CVERecord?id=CVE-2023-45853 Référence CVE CVE-2023-4641 https://www.cve.org/CVERecord?id=CVE-2023-4641 Référence CVE CVE-2023-4752 https://www.cve.org/CVERecord?id=CVE-2023-4752 Référence CVE CVE-2023-4807 https://www.cve.org/CVERecord?id=CVE-2023-4807 Référence CVE CVE-2023-48161 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0256Multiples vulnérabilités dans Broadcom VMware Tanzu Greenplum

d?id=CVE-2023-29409 Référence CVE CVE-2023-39318 https://www.cve.org/CVERecord?id=CVE-2023-39318 Référence CVE CVE-2023-39319 https://www.cve.org/CVERecord?id=CVE-2023-39319 Référence CVE CVE-2023-39323 https://www.cve.org/CVERecord?id=CVE-2023-39323 Référence CVE CVE-2023-39326 https://www.cve.org/CVERecord?id=CVE-2023-39326 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Référence CVE CVE-2023-45283 https://www.cve.org/CVERecord?id=CVE-2023-45283 Référence CVE CVE-2023-45284 https://www.cve.org/CVERecord?id=CVE-2023-45284 Référence CVE CVE-2023-45285 https://www.cve.org/CVERecord?id=CVE-2023-45285 Référence CVE CVE-2023-45287 https://www.cve.org/CVERecord?id=CVE-2023-45287 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-45289 https://www.cve.org/CVERecord?id=CVE-2023-45289 Référence CVE CVE-2023-45290 https://www.cve.org/CVERecord?id=CVE-2023-45290 Référence CVE CVE-2024-24783 https://www.cve.org/CVERecord?id=CVE-2024-24783 Référence CVE CVE-2024-24784 https://www.cve.org/CVERecord?id=CVE-2024-24784 Référence CVE CVE-2024-24785 https://www.cve.org/CVERecord?id=CVE-2024-24785 Référence CVE CVE-2024-24787 https://www.cve.org/CVERecord?id=CVE-2024-24787 Référence CVE CVE-2024-24789 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1104Vulnérabilité dans les produits NetApp

Une vulnérabilité a été découverte dans les produits NetApp. Elle permet à un attaquant de provoquer une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0741Multiples vulnérabilités dans Juniper Secure Analytics

d?id=CVE-2023-39318 Référence CVE CVE-2023-39319 https://www.cve.org/CVERecord?id=CVE-2023-39319 Référence CVE CVE-2023-39321 https://www.cve.org/CVERecord?id=CVE-2023-39321 Référence CVE CVE-2023-39322 https://www.cve.org/CVERecord?id=CVE-2023-39322 Référence CVE CVE-2023-39326 https://www.cve.org/CVERecord?id=CVE-2023-39326 Référence CVE CVE-2023-43788 https://www.cve.org/CVERecord?id=CVE-2023-43788 Référence CVE CVE-2023-43789 https://www.cve.org/CVERecord?id=CVE-2023-43789 Référence CVE CVE-2023-43804 https://www.cve.org/CVERecord?id=CVE-2023-43804 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Référence CVE CVE-2023-45287 https://www.cve.org/CVERecord?id=CVE-2023-45287 Référence CVE CVE-2023-45802 https://www.cve.org/CVERecord?id=CVE-2023-45802 Référence CVE CVE-2023-45803 https://www.cve.org/CVERecord?id=CVE-2023-45803 Référence CVE CVE-2023-4692 https://www.cve.org/CVERecord?id=CVE-2023-4692 Référence CVE CVE-2023-4693 https://www.cve.org/CVERecord?id=CVE-2023-4693 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2023-5090 https://www.cve.org/CVERecord?id=CVE-2023-5090 Référence CVE CVE-2023-52425 https://www.cve.org/CVERecord?id=CVE-2023-52425 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-20

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

d?id=CVE-2023-39321 Référence CVE CVE-2023-39322 https://www.cve.org/CVERecord?id=CVE-2023-39322 Référence CVE CVE-2023-39323 https://www.cve.org/CVERecord?id=CVE-2023-39323 Référence CVE CVE-2023-39325 https://www.cve.org/CVERecord?id=CVE-2023-39325 Référence CVE CVE-2023-39326 https://www.cve.org/CVERecord?id=CVE-2023-39326 Référence CVE CVE-2023-42282 https://www.cve.org/CVERecord?id=CVE-2023-42282 Référence CVE CVE-2023-45283 https://www.cve.org/CVERecord?id=CVE-2023-45283 Référence CVE CVE-2023-45284 https://www.cve.org/CVERecord?id=CVE-2023-45284 Référence CVE CVE-2023-45285 https://www.cve.org/CVERecord?id=CVE-2023-45285 Référence CVE CVE-2023-45287 https://www.cve.org/CVERecord?id=CVE-2023-45287 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-45289 https://www.cve.org/CVERecord?id=CVE-2023-45289 Référence CVE CVE-2023-45290 https://www.cve.org/CVERecord?id=CVE-2023-45290 Référence CVE CVE-2023-45803 https://www.cve.org/CVERecord?id=CVE-2023-45803 Référence CVE CVE-2023-46604 https://www.cve.org/CVERecord?id=CVE-2023-46604 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2023-51767 https://www.cve.org/CVERecord?id=CVE-2023-51767 Référence CVE CVE-2023-52425 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-019119The Go Project の Go における観測可能な不一致に関する脆弱性

The Go Project の Go には、観測可能な不一致に関する脆弱性が存在します。

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
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.
Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

  • Go 1.20 is released →Original publisher ↗Searchable text snapshot · Captured 29 Sep 2026Groups Groups Conversations All groups and messages Send feedback to Google Help Training Sign in Groups Groups Conversations About     Go 1.20 is released 2,443 views Skip to first unread message  Michael Knyszek unread, Feb 1, 2023, 8:37:12 PM 2/1/23    Reply to author Sign in to reply to author F
04

Evidence and provenance

Published 5 Dec 2023 · Last source change 13 Feb 2025, 17:14 UTC · CWE-208 · Observable Timing 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-49587
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.20.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 1.20.0 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2023-49587↗Red Hat Product Security security advisory↗Vendor advisory↗CVE authority or vendor 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.
Free version - for non-commercial use only.CVE-2023-45287 · cve.blacktree.nl