# CVE-2023-37918: API token authentication bypass in HTTP endpoints in Dapr

> Attackers can bypass API token authentication in Dapr sidecars via crafted HTTP requests, requiring users with this feature enabled to upgrade.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2023
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-59m6-82qm-vqgj, GO-2023-1955

## What is CVE-2023-37918?

CVE-2023-37918 is a medium-severity authentication bypass vulnerability in dapr, published on 21 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge. A vulnerability has been found in Dapr that allows bypassing API token authentication, which is used by the Dapr sidecar to authenticate calls coming from the application, with a well-crafted HTTP request. Users who leverage API token authentication are encouraged to upgrade Dapr to 1.10.9 or to 1.11.2. This vulnerability impacts Dapr users who have configured API token authentication. An attacker could craft a request that is always allowed by the Dapr sidecar over HTTP, even if the `dapr-api-token` in the request is invalid or missing. The issue has been fixed in Dapr 1.10.9 or to 1.11.2. There are no known workarounds for this vulnerability.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-37918?

5 open source packages ship an affected version, including github.com/dapr/dapr. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/dapr/dapr` | Go | All versions | 1.10.9, 1.11.2 |
| `github.com/dapr/dapr` | Go | All versions | 1.10.9 |
| `github.com/dapr/dapr` | Go | All versions | 1.10.9 |
| `github.com/dapr/dapr` | Go | From 1.11.0 | 1.11.2 |
| `github.com/dapr/dapr` | Go | From 1.11.0 | 1.11.2 |

Products: Linuxfoundation Dapr.

## How do I fix CVE-2023-37918?

Upgrade github.com/dapr/dapr to a fixed version for your release line: 1.10.9 or 1.11.2.

## Is CVE-2023-37918 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-37918 exists.

## Other vulnerabilities in dapr

- [CVE-2026-41491](https://insights.sbomify.com/CVE-2026-41491/): Dapr: Service Invocation path traversal ACL bypass (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-37918 and fix it if it is affected.

What it is: CVE-2023-37918 is a medium-severity authentication bypass vulnerability in dapr, published on 21 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-37918 exists.

Affected packages and fixed versions:
- github.com/dapr/dapr (Go): affected all versions; fixed in 1.10.9, 1.11.2
- github.com/dapr/dapr (Go): affected all versions; fixed in 1.10.9
- github.com/dapr/dapr (Go): affected all versions; fixed in 1.10.9
- github.com/dapr/dapr (Go): affected from 1.11.0; fixed in 1.11.2
- github.com/dapr/dapr (Go): affected from 1.11.0; fixed in 1.11.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-37918/ (Markdown: https://insights.sbomify.com/CVE-2023-37918/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-37918
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-37918
- OSV: https://osv.dev/vulnerability/CVE-2023-37918

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-37918/
Summaries are generated and may contain mistakes; the official description above is the record.