Container suse/manager/5.0/x86_64/server:5.0.5…: Missing Authorization
CVE-2025-46811 is a critical-severity missing authorization vulnerability in Container suse/manager/5.0/x86_64/server:5.0.5.7.30.1 from SUSE, 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 version 5.0.27-150600.3.33.1 as the first without the flaw, so updating Container suse/manager/5.0/x86_64/server:5.0.5.7.30.1 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 13.6% chance of exploitation within 30 days, which is in the top 3.47% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Container suse/manager/5.0/x86_64/server:5.0.5.7.30.1 to 5.0.27-150600.3.33.1 or a later version.
- Update Image SLES15-SP4-Manager-Server-4-3-BYOS to 4.3.87-150400.3.110.2 or a later version.
- Update Image SLES15-SP4-Manager-Server-4-3-BYOS-Azure to 4.3.87-150400.3.110.2 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 |
|---|---|---|---|
| SUSE | Container suse/manager/5.0/x86_64/server:5.0.5.7.30.1 | ? up to, but not including, 5.0.27-150600.3.33.1 | 5.0.27-150600.3.33.1 |
| SUSE | Image SLES15-SP4-Manager-Server-4-3-BYOS | ? up to, but not including, 4.3.87-150400.3.110.2 | 4.3.87-150400.3.110.2 |
| SUSE | Image SLES15-SP4-Manager-Server-4-3-BYOS-Azure | ? up to, but not including, 4.3.87-150400.3.110.2 | 4.3.87-150400.3.110.2 |
| SUSE | Image SLES15-SP4-Manager-Server-4-3-BYOS-EC2 | ? up to, but not including, 4.3.87-150400.3.110.2 | 4.3.87-150400.3.110.2 |
| SUSE | Image SLES15-SP4-Manager-Server-4-3-BYOS-GCE | ? up to, but not including, 4.3.87-150400.3.110.2 | 4.3.87-150400.3.110.2 |
| SUSE | SUSE Manager Server Module 4.3 | ? up to, but not including, 4.3.87-150400.3.110.2 | 4.3.87-150400.3.110.2 |
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 CNA (suse.de).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.3 | Critical | CNA (suse.de) |
| CVSS 3.1 | 9.8 | Critical | CNA (suse.de) |
Official description
A Missing Authorization vulnerability in SUSE Linux Manager allows anyone with the ability to connect to port 443 of SUSE Manager is able to run any command as root on any client. This issue affects Container suse/manager/5.0/x86_64/server:5.0.5.7.30.1: from ? before 5.0.27-150600.3.33.1; Image SLES15-SP4-Manager-Server-4-3-BYOS: from ? before 4.3.87-150400.3.110.2; Image SLES15-SP4-Manager-Server-4-3-BYOS-Azure: from ? before 4.3.87-150400.3.110.2; Image SLES15-SP4-Manager-Server-4-3-BYOS-EC2: from ? before 4.3.87-150400.3.110.2; Image SLES15-SP4-Manager-Server-4-3-BYOS-GCE: from ? before 4.3.87-150400.3.110.2; SUSE Manager Server Module 4.3: from ? before 4.3.87-150400.3.110.2.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Missing Authorization vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.