CVE-2022-24715: Arbitrary code execution for authenticated users in Icinga Web 2
Noroxi assessment
Priority: Monitor (action score 39/100)
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 14.8% (FIRST EPSS); higher than 96.6% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: icingaweb2 (Debian:12) 2.9.6-1; icingaweb2 (openSUSE:Leap 15.3) 2.8.6-bp153.2.3.1; icingaweb2 (SUSE:Package Hub 12) 2.8.6-15.1.
Low priority for now. Upgrade to icingaweb2 (Debian:12) 2.9.6-1; icingaweb2 (openSUSE:Leap 15.3) 2.8.6-bp153.2.3.1; icingaweb2 (SUSE:Package Hub 12) 2.8.6-15.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Icinga Web 2 is an open source monitoring web interface, framework and command-line interface. Authenticated users, with access to the configuration, can create SSH resource files in unintended directories, leading to the execution of arbitrary code. This issue has been resolved in versions 2.8.6, 2.9.6 and 2.10 of Icinga Web 2. Users unable to upgrade should limit access to the Icinga Web 2 configuration.
- Published
- Mar 8, 2022
- Updated
- Jun 17, 2026
- EPSS
- 14.8% · 96th percentile
- CWE
- CWE-22
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 14.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · GitHub_M
- 8.5
- 0.3 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| icinga | icinga web 2 | cpe:2.3:a:icinga:icinga_web_2 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- icinga icinga web 2before 2.8.6
- icinga icinga web 22.9.0 and later · before 2.9.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
Icinga icingaweb2
- < 2.8.6, >= 2.9.0, < 2.9.6affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | icingaweb2 | before 2.9.6-1 | 2.9.6-1 |
| openSUSE:Leap 15.3 | icingaweb2 | before 2.8.6-bp153.2.3.1 | 2.8.6-bp153.2.3.1 |
| SUSE:Package Hub 12 | icingaweb2 | before 2.8.6-15.1 | 2.8.6-15.1 |
| SUSE:Package Hub 15 SP3 | icingaweb2 | before 2.8.6-bp153.2.3.1 | 2.8.6-bp153.2.3.1 |
Same product
icinga: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-24716Path traversal in Icinga Web 260This week
- CVE-2018-18249Icinga Web 2 before 2.6.2 allows injection of PHP ini-file directives via vectors involving environment variables as the channel to send inf39Monitor
- CVE-2020-24368Icinga Icinga Web2 2.0.0 through 2.6.4, 2.7.4 and 2.8.2 has a Directory Traversal vulnerability which allows an attacker to access arbitrary31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2018-18250Dec 17, 2018 · Icinga Web 2 before 2.6.2 allows parameters that break navigation dashlets, as demonstrated by a single '$' character as the Name of a Navig30Monitor
- ← EarlierCVE-2022-24714Mar 8, 2022 · Disclosure of hosts and related data, linked to decommissioned services in Icinga Web 221Monitor
- Later →CVE-2025-27404Mar 26, 2025 · Icinga Web 2 DOM-based XSS vulnerability24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:icingaweb2 | 2.9.6-1 · Debian:12 | Package registry (OSV) |
| opensuse:icingaweb2 | 2.8.6-bp153.2.3.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| suse:icingaweb2 | 2.8.6-15.1 · SUSE:Package Hub 12 | Package registry (OSV) |
| suse:icingaweb2 | 2.8.6-bp153.2.3.1 · SUSE:Package Hub 15 SP3 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×3
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2023-07-15 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-03-25 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-07-08 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-11-06 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+381 d
- TodayOct 31, 2026+1698 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.