# CVE-2022-0983: SQL Injection in Moodle

> Teachers and managers can exploit SQL injection in Moodle Badges criteria configuration to read or modify database data.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** BIT-moodle-2022-0983, GHSA-h2fw-93qx-vrcq, UBUNTU-CVE-2022-0983

## What is CVE-2022-0983?

CVE-2022-0983 is a high-severity SQL injection vulnerability in Fedoraproject Extra Packages for Enterprise Linux, published on 25 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An SQL injection risk was identified in Badges code relating to configuring criteria. Access to the relevant capability was limited to teachers and managers by default.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

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 | All versions | 3.9.13 |
| `moodle/moodle` | Packagist | All versions | 3.9.13 |
| `moodle/moodle` | Packagist | From 3.10.0 | 3.10.10 |
| `moodle/moodle` | Packagist | From 3.10.0 | 3.10.10 |
| `moodle/moodle` | Packagist | From 3.11.0 | 3.11.6 |
| `moodle/moodle` | Packagist | From 3.11.0 | 3.11.6 |
| `moodle` | Bitnami | From 3.9.0 | 3.9.13, 3.10.10, 3.11.6 |

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

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

Upgrade moodle/moodle to a fixed version for your release line: 3.9.13, 3.10.10 or 3.11.6.

## Is CVE-2022-0983 being exploited?

There is no known exploitation of CVE-2022-0983 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-45152](https://insights.sbomify.com/CVE-2022-45152/): Moodle blind Server-Side Request Forgery (SSRF) vulnerability in LTI provider library (critical 9.1)
- [CVE-2022-24882](https://insights.sbomify.com/CVE-2022-24882/): Server side NTLM does not properly check parameters in FreeRDP (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0983 is a high-severity SQL injection vulnerability in Fedoraproject Extra Packages for Enterprise Linux, published on 25 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0983 in the wild and no public exploit code.

Affected packages and fixed versions:
- moodle/moodle (Packagist): affected all versions; fixed in 3.9.13
- moodle/moodle (Packagist): affected all versions; fixed in 3.9.13
- moodle/moodle (Packagist): affected from 3.10.0; fixed in 3.10.10
- moodle/moodle (Packagist): affected from 3.10.0; fixed in 3.10.10
- moodle/moodle (Packagist): affected from 3.11.0; fixed in 3.11.6
- moodle/moodle (Packagist): affected from 3.11.0; fixed in 3.11.6
- moodle (Bitnami): affected from 3.9.0; fixed in 3.9.13, 3.10.10, 3.11.6

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

## Sources

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

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