# CVE-2024-47218: Auth bypass in n/a

> Attackers can bypass authentication in NebulaGraph, potentially gaining unauthorized access to the database system.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2024
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-9p6f-43f7-gmq3, GO-2024-3155

## What is CVE-2024-47218?

CVE-2024-47218 is a critical authentication bypass vulnerability in n/a, published on 22 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in vesoft NebulaGraph through 3.8.0. It allows bypassing authentication.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-47218?

1 open source package ship an affected version, including github.com/vesoft-inc/nebula. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/vesoft-inc/nebula` | Go | All versions | None |

Products: Vesoft Nebulagraph Database.

## How do I fix CVE-2024-47218?

No fix has been published for CVE-2024-47218 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-47218 being exploited?

There is no known exploitation of CVE-2024-47218 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-47219](https://insights.sbomify.com/CVE-2024-47219/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47218 and fix it if it is affected.

What it is: CVE-2024-47218 is a critical authentication bypass vulnerability in n/a, published on 22 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47218 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/vesoft-inc/nebula (Go): affected all versions; no fix listed

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-2024-47218/ (Markdown: https://insights.sbomify.com/CVE-2024-47218/index.md)
```

## Sources

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

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