# CVE-2024-37775: Missing authorization in n/a

> Attackers can bypass RBAC checks to create or update tickets with unauthorized locations in Sunbird DCIM dcTrack.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-9c83-cg8h-x7rp

## What is CVE-2024-37775?

CVE-2024-37775 is a high-severity missing authorization vulnerability in n/a, published on 16 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in Sunbird DCIM dcTrack v9.1.2 allows attackers to create or update a ticket with a location which bypasses an RBAC check.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Sunbirddcim Dctrack.

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

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

## Is CVE-2024-37775 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-37774](https://insights.sbomify.com/CVE-2024-37774/): Cross-site request forgery in n/a (high 8.0)
- [CVE-2024-37773](https://insights.sbomify.com/CVE-2024-37773/): Cross-site scripting in n/a (medium 4.8)
- [CVE-2024-37776](https://insights.sbomify.com/CVE-2024-37776/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37775 is a high-severity missing authorization vulnerability in n/a, published on 16 Dec 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-37775 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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