# CVE-2024-5526: Server-side request forgery in OnCall

> Attackers can exploit a Server Side Request Forgery vulnerability in Grafana OnCall's webhook functionality to access internal resources.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-5cwx-g8mg-7v9c

## What is CVE-2024-5526?

CVE-2024-5526 is a high-severity server-side request forgery vulnerability in Grafana OnCall, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grafana OnCall is an easy-to-use on-call management tool that will help reduce toil in on-call management through simpler workflows and interfaces that are tailored specifically for engineers.

Grafana OnCall, from version 1.1.37 before 1.5.2 are vulnerable to a Server Side Request Forgery (SSRF) vulnerability in the webhook functionallity. 

This issue was fixed in version 1.5.2

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Grafana Oncall.

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

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

## Is CVE-2024-5526 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5526 is a high-severity server-side request forgery vulnerability in Grafana OnCall, published on 5 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5526 in the wild and no public exploit code.

Affected product: Grafana OnCall. 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-5526/ (Markdown: https://insights.sbomify.com/CVE-2024-5526/index.md)
```

## Sources

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

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