CVE-2023-37918: GO-2023-1955 - Dapr API token authentication bypass in HTTP endpoints in github.com/dapr/dapr

CVE-2023-37918 · Severity: low · CVSS 3.1 · Published 2024-08-20

Dapr API token authentication bypass in HTTP endpoints in github.com/dapr/dapr

Technologies: github.com/dapr/dapr (Go). Vendors: Go.

Quick answers

Is CVE-2023-37918 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-37918 being exploited in the wild.
How severe is CVE-2023-37918?
Low severity, with a CVSS score of 3.1, published 20 August 2024.
Which products and versions are affected?
github.com/dapr/dapr (Go) SEMVER:introduced=0,fixed=1.10.9,introduced=1.11.0,fixed=1.11.2, SEMVER:introduced=1.11.0,fixed=1.11.2.
Is there a fix for CVE-2023-37918?
Yes. github.com/dapr/dapr (Go): upgrade to 1.11.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-37918?
Check whether you run github.com/dapr/dapr (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/dapr/dapr (Go): upgrade to 1.11.2 or later
    go get github.com/dapr/dapr@v1.11.2

Affected products

  • github.com/dapr/dapr (Go) SEMVER:introduced=0,fixed=1.10.9,introduced=1.11.0,fixed=1.11.2, SEMVER:introduced=1.11.0,fixed=1.11.2

Identifiers

  • CVE-2023-37918
  • GHSA-59m6-82qm-vqgj
  • GO-2023-1955

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.