Information Exposure Affecting grafana-opentsdb package, versions *


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.08% (37th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-GRAFANAOPENTSDB-6104768
  • published7 Dec 2023
  • disclosed5 Dec 2023

Introduced: 5 Dec 2023

CVE-2023-45287  (opens in a new tab)
CWE-208  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 grafana-opentsdb.

NVD Description

Note: Versions mentioned in the description apply only to the upstream grafana-opentsdb package and not the grafana-opentsdb package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1