# CVE-2022-45152: Moodle blind Server-Side Request Forgery (SSRF) vulnerability in LTI provider library

> Remote attackers can exploit insufficient input validation in the LTI provider library to perform blind Server-Side Request Forgery attacks against arbitrary systems.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** Yes
- **Published:** 25 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** BIT-moodle-2022-45152, GHSA-xqcf-vgqc-pcmg, UBUNTU-CVE-2022-45152

## What is CVE-2022-45152?

CVE-2022-45152 is a critical server-side request forgery vulnerability in Fedoraproject Extra Packages for Enterprise Linux, published on 25 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A blind Server-Side Request Forgery (SSRF) vulnerability was found in Moodle. This flaw exists due to insufficient validation of user-supplied input in LTI provider library. The library does not utilise Moodle's inbuilt cURL helper, which resulted in a blind SSRF risk. An attacker can send a specially crafted HTTP request and trick the application to initiate requests to arbitrary systems. This vulnerability allows a remote attacker to perform SSRF attacks.

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

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

7 open source packages ship an affected version, including moodle/moodle and moodle. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `moodle/moodle` | Packagist | From 3.11 | 3.11.11 |
| `moodle/moodle` | Packagist | From 3.11 | 3.11.11 |
| `moodle/moodle` | Packagist | From 3.9 | 3.9.18 |
| `moodle/moodle` | Packagist | From 3.9 | 3.9.18 |
| `moodle/moodle` | Packagist | From 4.0 | 4.0.5 |
| `moodle/moodle` | Packagist | From 4.0 | 4.0.5 |
| `moodle` | Bitnami | All versions | 3.9.18, 3.11.11, 4.0.5 |

Products: Fedoraproject Extra Packages for Enterprise Linux, Fedoraproject Fedora, Moodle Moodle.

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

Upgrade moodle/moodle to a fixed version for your release line: 3.11.11, 3.9.18 or 4.0.5.

## Is CVE-2022-45152 being exploited?

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

## Other vulnerabilities in Fedoraproject Extra Packages for Enterprise Linux

- [CVE-2023-34152](https://insights.sbomify.com/CVE-2023-34152/): Command injection in ImageMagick (critical 9.8)
- [CVE-2022-4170](https://insights.sbomify.com/CVE-2022-4170/): Code injection in rxvt-unicode (critical 9.8)
- [CVE-2022-40315](https://insights.sbomify.com/CVE-2022-40315/): Moodle Minor SQL injection risk in admin user browsing (critical 9.8)
- [CVE-2022-24882](https://insights.sbomify.com/CVE-2022-24882/): Server side NTLM does not properly check parameters in FreeRDP (critical 9.1)
- [CVE-2022-2158](https://insights.sbomify.com/CVE-2022-2158/): Use after free in Chrome (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45152 is a critical server-side request forgery vulnerability in Fedoraproject Extra Packages for Enterprise Linux, published on 25 Nov 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-45152 in the wild and no public exploit code.

Affected packages and fixed versions:
- moodle/moodle (Packagist): affected from 3.11; fixed in 3.11.11
- moodle/moodle (Packagist): affected from 3.11; fixed in 3.11.11
- moodle/moodle (Packagist): affected from 3.9; fixed in 3.9.18
- moodle/moodle (Packagist): affected from 3.9; fixed in 3.9.18
- moodle/moodle (Packagist): affected from 4.0; fixed in 4.0.5
- moodle/moodle (Packagist): affected from 4.0; fixed in 4.0.5
- moodle (Bitnami): affected all versions; fixed in 3.9.18, 3.11.11, 4.0.5

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

## Sources

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

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