moodle: QR login key and auto-login key for the Moodle mobile app should be generated as separate keys (CVE-2024-38277)
CVE-2024-38277 is a vulnerability in Moodle where the QR login key and the auto-login key for the Moodle mobile app are not generated as separate unique keys. This allows the same key to be used interchangeably between QR login and auto-login, which is not intended behavior. The issue affects multiple Moodle versions prior to specific patch releases. A patch is available to address this issue.
AI Analysis
Technical Summary
The vulnerability CVE-2024-38277 in Moodle arises because the QR login key and the auto-login key for the Moodle mobile app are generated using the same key. This design flaw means that the same key can be used interchangeably for both login methods, potentially weakening the authentication mechanism. The problem affects Moodle versions 4.1.0 up to but not including 4.1.11, 4.2.0 up to but not including 4.2.8, 4.3.0 up to but not including 4.3.5, and 4.4.0 up to but not including 4.4.1. A patch is available to generate unique keys for each login method, mitigating the issue.
Potential Impact
The impact is a medium-severity authentication weakness where the same key can be used for both QR login and auto-login in the Moodle mobile app. This could potentially allow unintended reuse of authentication tokens, weakening the security model of user authentication. There are no known exploits in the wild reported at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade to Moodle versions 4.1.11 or later, 4.2.8 or later, 4.3.5 or later, or 4.4.1 or later to ensure that QR login keys and auto-login keys are generated separately. Applying the official patch resolves the issue.
moodle: QR login key and auto-login key for the Moodle mobile app should be generated as separate keys (CVE-2024-38277)
Description
CVE-2024-38277 is a vulnerability in Moodle where the QR login key and the auto-login key for the Moodle mobile app are not generated as separate unique keys. This allows the same key to be used interchangeably between QR login and auto-login, which is not intended behavior. The issue affects multiple Moodle versions prior to specific patch releases. A patch is available to address this issue.
Affected software
pkg:bitnami/moodleRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2024-38277 in Moodle arises because the QR login key and the auto-login key for the Moodle mobile app are generated using the same key. This design flaw means that the same key can be used interchangeably for both login methods, potentially weakening the authentication mechanism. The problem affects Moodle versions 4.1.0 up to but not including 4.1.11, 4.2.0 up to but not including 4.2.8, 4.3.0 up to but not including 4.3.5, and 4.4.0 up to but not including 4.4.1. A patch is available to generate unique keys for each login method, mitigating the issue.
Potential Impact
The impact is a medium-severity authentication weakness where the same key can be used for both QR login and auto-login in the Moodle mobile app. This could potentially allow unintended reuse of authentication tokens, weakening the security model of user authentication. There are no known exploits in the wild reported at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade to Moodle versions 4.1.11 or later, 4.2.8 or later, 4.3.5 or later, or 4.4.1 or later to ensure that QR login keys and auto-login keys are generated separately. Applying the official patch resolves the issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-moodle-2024-38277
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2024-38277"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
Threat ID: 6aa00615acd9273b49ab7759
Added to database: 09/08/2026, 12:56:53 UTC
Last enriched: 09/08/2026, 13:43:01 UTC
Last updated: 09/10/2026, 19:36:48 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.