CVE-2024-28832
Medium · 4.8CVSS
4.8
EPSS
0.3%
Published
Jun 25, 2024
CISA due date
—
Cloudanix analysis
Someone with certain admin rights could hide harmful code in a settings field that runs when others open a specific page, potentially letting them take over those users' accounts.
- Exploitation
- Remote Authenticated
- Attacker needs
- High Privilege
- Complexity
- Moderate
- Impact
- Data Tampering
- Component
- Application
- Class
- XSS
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Allows users with Global Settings modification rights to store arbitrary HTML and JavaScript in the Crash Report URL field, which is rendered without sanitization on the Crash Report page, resulting in script execution in viewers' browsers.
Why it matters to the business
Compromised privileged accounts could lead to session hijacking against other administrators, exposing monitoring configurations, alert data, and infrastructure visibility across the environment.
How an attack unfolds
An attacker with Global Settings access injects a malicious payload into the Crash Report URL setting; the stored content executes when any user loads the Crash Report page, allowing actions such as cookie theft or unauthorized configuration changes.
How to fix it
Upgrade Checkmk to 2.3.0p7, 2.2.0p28, 2.1.0p45 or later. On Debian 13 systems, install package version 6.7.9-1 or newer.
How to confirm the fix worked
Confirm the running Checkmk version meets or exceeds the listed fixed releases and inspect the Crash Report URL setting to ensure input sanitization prevents HTML or script injection.
Typical attack path
- Obtain or compromise an account permitted to change Global Settings
- Navigate to Global Settings and locate the Crash Report URL option
- Insert HTML or script elements containing attacker-controlled code
- Trigger or wait for a user to view the Crash Report page
- Execute actions in the context of the viewing user's session
How to detect it
Examine stored Global Settings for HTML or script content in the Crash Report URL field and search web server logs for requests to the Crash Report page containing unusual parameters or referrers.
- Crash Report URL containing <script
- javascript: in global settings value
- unusual HTML tags persisted in crash report configuration
What your security team should do
- Apply the specified Checkmk updates without delay
- Audit all Global Settings entries for unexpected content in the Crash Report URL field
- Restrict Global Settings permissions to the minimum necessary accounts
- Review web access logs for anomalous Crash Report page activity
The record
Stored XSS in the Crash Report page in Checkmk before versions 2.3.0p7, 2.2.0p28, 2.1.0p45, and 2.0.0 (EOL) allows users with permission to change Global Settings to execute arbitrary scripts by injecting HTML elements into the Crash Report URL in the Global Settings.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Ubuntu:18.04:LTS | check-mk | 0 | No fix |
| Ubuntu:Pro:16.04:LTS | check-mk | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | check-mk | 0 | No fix |
Related vulnerabilities
- CVE-2024-47094 Insertion of Sensitive Information into Log File in Checkmk GmbH's Checkmk versions… Also affects check-mk
- CVE-2024-38863 Exposure of CSRF tokens in query parameters on specific requests in Checkmk GmbH's… Also affects check-mk
- CVE-2024-38862 Insertion of Sensitive Information into Log File in Checkmk GmbH's Checkmk versions… Also affects check-mk
- CVE-2024-6747 Information leakage in mknotifyd in Checkmk before 2.3.0p18, 2.2.0p36, 2.1.0p49 and in… Also affects check-mk
- CVE-2024-8606 Bypass of two factor authentication in RestAPI in Checkmk < 2.3.0p16 and < 2.2.0p34… Also affects check-mk
- CVE-2024-38860 Improper neutralization of input in Checkmk before versions 2.3.0p16 and 2.2.0p34 allows… Also affects check-mk
- CVE-2024-38858 Improper neutralization of input in Checkmk before version 2.3.0p14 allows attackers to… Also affects check-mk
- CVE-2024-38859 XSS in the view page with the SLA column configured in Checkmk versions prior to… Also affects check-mk