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

> Attackers can exploit Server-Side Request Forgery in SLiMS to access internal resources or bypass security controls.

- **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:** 12 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5658-g88g-9pmw

## What is CVE-2022-38292?

CVE-2022-38292 is a critical server-side request forgery vulnerability in n/a, published on 12 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SLiMS Senayan Library Management System v9.4.2 was discovered to contain multiple Server-Side Request Forgeries via the components /bibliography/marcsru.php and /bibliography/z3950sru.php.

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

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

It affects 1 product.


Products: Slims Senayan Library Management System.

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

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

## Is CVE-2022-38292 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-3744](https://insights.sbomify.com/CVE-2023-3744/): Server-Side Request Forgery in SLiMS (critical 9.9)
- [CVE-2023-45996](https://insights.sbomify.com/CVE-2023-45996/): SQL injection in n/a (high 8.8)
- [CVE-2023-40970](https://insights.sbomify.com/CVE-2023-40970/): SQL injection in n/a (high 8.8)
- [CVE-2021-45791](https://insights.sbomify.com/CVE-2021-45791/): SQL injection in n/a (high 8.8)
- [CVE-2017-12584](https://insights.sbomify.com/CVE-2017-12584/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38292 is a critical server-side request forgery vulnerability in n/a, published on 12 Sep 2022. 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-2022-38292 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-2022-38292/ (Markdown: https://insights.sbomify.com/CVE-2022-38292/index.md)
```

## Sources

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

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