# CVE-2024-38277: moodle: QR login key and auto-login key for the Moodle mobile app should be generated as separate keys

> Attackers can reuse a single key for both QR login and auto-login, potentially bypassing authentication controls in the Moodle mobile app.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** Yes
- **Published:** 18 Jun 2024
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-moodle-2024-38277, GHSA-r82w-3phg-qvr4

## What is CVE-2024-38277?

CVE-2024-38277 is a medium-severity vulnerability in Fedoraproject Fedora, published on 18 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A unique key should be generated for a user's QR login key and their auto-login key, so the same key cannot be used interchangeably between the two.

Weakness: CWE-326 (Inadequate Encryption Strength), CWE-324 (Use of a Key Past its Expiration Date)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `moodle/moodle` | Packagist | All versions | 4.1.11 |
| `moodle/moodle` | Packagist | All versions | 4.1.11 |
| `moodle/moodle` | Packagist | From 4.2.0-beta | 4.2.8 |
| `moodle/moodle` | Packagist | From 4.2.0-beta | 4.2.8 |
| `moodle/moodle` | Packagist | From 4.3.0-beta | 4.3.5 |
| `moodle/moodle` | Packagist | From 4.3.0-beta | 4.3.5 |
| `moodle/moodle` | Packagist | From 4.4.0-beta | 4.4.1 |
| `moodle/moodle` | Packagist | From 4.4.0-beta | 4.4.1 |
| `moodle` | Bitnami | From 4.1.0 | 4.1.11, 4.2.8, 4.3.5, 4.4.1 |

Products: Fedoraproject Fedora, Moodle Moodle.

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

Upgrade moodle/moodle to a fixed version for your release line: 4.1.11, 4.2.8, 4.3.5 or 4.4.1.

## Is CVE-2024-38277 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38277 is a medium-severity vulnerability in Fedoraproject Fedora, published on 18 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-38277 in the wild and no public exploit code.

Affected packages and fixed versions:
- moodle/moodle (Packagist): affected all versions; fixed in 4.1.11
- moodle/moodle (Packagist): affected all versions; fixed in 4.1.11
- moodle/moodle (Packagist): affected from 4.2.0-beta; fixed in 4.2.8
- moodle/moodle (Packagist): affected from 4.2.0-beta; fixed in 4.2.8
- moodle/moodle (Packagist): affected from 4.3.0-beta; fixed in 4.3.5
- moodle/moodle (Packagist): affected from 4.3.0-beta; fixed in 4.3.5
- moodle/moodle (Packagist): affected from 4.4.0-beta; fixed in 4.4.1
- moodle/moodle (Packagist): affected from 4.4.0-beta; fixed in 4.4.1
- moodle (Bitnami): affected from 4.1.0; fixed in 4.1.11, 4.2.8, 4.3.5, 4.4.1

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

## Sources

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

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