# CVE-2022-41412: Server-side request forgery in n/a

> Attackers can exploit the graphData.cgi component to access sensitive data and perform Server-Side Request Forgery attacks.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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:** 30 Nov 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-qvfg-q6v8-7jx8

## What is CVE-2022-41412?

CVE-2022-41412 is a high-severity server-side request forgery vulnerability in n/a, published on 30 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the graphData.cgi component of perfSONAR v4.4.5 and prior allows attackers to access sensitive data and execute Server-Side Request Forgery (SSRF) attacks.

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

## Which versions are affected by CVE-2022-41412?

It affects 1 product.


Products: Perfsonar Perfsonar.

## How do I fix CVE-2022-41412?

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

## Is CVE-2022-41412 being exploited?

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

Public exploit code:

- perfSONAR 4.x <= 4.4.4 - Server-Side Request Forgery (nuclei): http/cves/2022/CVE-2022-41412.yaml

## Other vulnerabilities in n/a

- [CVE-2022-45027](https://insights.sbomify.com/CVE-2022-45027/): Server-side request forgery in n/a (medium 5.3)
- [CVE-2022-45213](https://insights.sbomify.com/CVE-2022-45213/): Path traversal in n/a (medium 5.3)
- [CVE-2022-41413](https://insights.sbomify.com/CVE-2022-41413/): Cross-site request forgery in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41412 and fix it if it is affected.

What it is: CVE-2022-41412 is a high-severity server-side request forgery vulnerability in n/a, published on 30 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41412 exists.

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

## Sources

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

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