MAAS: Improper Authentication
CVE-2024-6107 is a critical-severity improper authentication vulnerability in MAAS from Canonical, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 3.1.4, 3.2.11, 3.3.8 as the first without the flaw, so updating MAAS to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.42% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update MAAS to 3.1.4 or 3.2.11 or 3.3.8 or 3.4.4, whichever matches your release line, or a later version.
- Update Metal As A Service to 3.1.4 or 3.2.11 or 3.3.8 or 3.4.4, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Canonical | MAAS | 3.1.0 up to, but not including, 3.1.4; 3.2.0 up to, but not including, 3.2.11; 3.3.0 up to, but not including, 3.3.8; 3.4.0 up to, but not including, 3.4.4; 3.5.0 up to, but not including, 3.5.1 | 3.1.4, 3.2.11, 3.3.8, 3.4.4, 3.5.1 |
| Canonical | Metal As A Service | 3.1.0 up to, but not including, 3.1.4; 3.2.0 up to, but not including, 3.2.11; 3.3.0 up to, but not including, 3.3.8; 3.4.0 up to, but not including, 3.4.4; 3.5.0 | 3.1.4, 3.2.11, 3.3.8, 3.4.4 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.6 | Critical | CNA (ubuntu.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
Due to insufficient verification, an attacker could use a malicious client to bypass authentication checks and run RPC commands in a region. This has been addressed in MAAS and updated in the corresponding snaps.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- bugs.launchpad.net/maas/+bug/2069094Exploit, Issue Tracking
Recent Improper Authentication vulnerabilities
- 7.8 High severity
- 7.5 High severity
- 9.8 Critical severity
- 7.1 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.