CVE-2024-10224: Qualys discovered that if unsanitized input was used with the library Modules::ScanDeps, before version 1.36 a local attacker could possibly…
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 8.9% (FIRST EPSS); higher than 95.3% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Module::ScanDeps Module::ScanDeps 1.38; azl3 perl-Module-ScanDeps 1.35-3 on Azure Linux 3.0 1.35-3; cbl2 perl-Module-ScanDeps 1.35-2 on CBL Mariner 2.0 1.35-2.
- Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 7.8.
Low priority for now. Upgrade to Module::ScanDeps Module::ScanDeps 1.38; azl3 perl-Module-ScanDeps 1.35-3 on Azure Linux 3.0 1.35-3; cbl2 perl-Module-ScanDeps 1.35-2 on CBL Mariner 2.0 1.35-2 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
Qualys discovered that if unsanitized input was used with the library Modules::ScanDeps, before version 1.36 a local attacker could possibly execute arbitrary shell commands by open()ing a "pesky pipe" (such as passing "commands|" as a filename) or by passing arbitrary strings to eval().
- Published
- Nov 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 8.9% · 95th percentile
- CWE
- CWE-78
Report tools
Action score
34
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 8.9%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · canonical
- 5.3
- 2.5 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| rschupp | modules\ | cpe:2.3:a:rschupp:modules\ |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (canonical). Independent of NVD's CPE analysis and usually ahead of it.
Module::ScanDeps Module::ScanDeps
- before 1.38affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- rschupp modules::scandepsbefore 1.36
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | perl-Module-ScanDeps | before 1.30-6.el9 | 1.30-6.el9 |
| Alpine:v3.21 | perl-module-scandeps | before 1.37-r0 | 1.37-r0 |
| Debian:11 | libmodule-scandeps-perl | before 1.30-1+deb11u1 | 1.30-1+deb11u1 |
| Debian:12 | libmodule-scandeps-perl | before 1.31-2+deb12u1 | 1.31-2+deb12u1 |
| Debian:13 | libmodule-scandeps-perl | before 1.35-2 | 1.35-2 |
| openSUSE:Tumbleweed | perl-Module-ScanDeps | before 1.370.0-1.1 | 1.370.0-1.1 |
| Red Hat:enterprise_linux:9::crb | perl-Module-ScanDeps | before 0:1.30-6.el9 | 0:1.30-6.el9 |
| Rocky Linux:9 | perl-Module-ScanDeps | before 0:1.30-6.el9 | 0:1.30-6.el9 |
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 |
|---|---|---|
| Module::ScanDeps Module::ScanDeps | 1.38 | Vendor (CNA) |
| azl3 perl-Module-ScanDeps 1.35-3 on Azure Linux 3.0 | 1.35-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 perl-Module-ScanDeps 1.35-2 on CBL Mariner 2.0 | 1.35-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 perl-Module-ScanDeps 1.35-3 on CBL Mariner 2.0 | 1.35-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 perl-Module-ScanDeps 1.35-3 on CBL-Mariner 2.0 | 1.35-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:perl-Module-ScanDeps | 1.30-6.el9 · AlmaLinux:9 | Package registry (OSV) |
| alpine:perl-module-scandeps | 1.37-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:libmodule-scandeps-perl | 1.31-2+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:perl-Module-ScanDeps | 1.370.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:perl-Module-ScanDeps | 0:1.30-6.el9 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| rocky linux:perl-Module-ScanDeps | 0:1.30-6.el9 · Rocky Linux:9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Qualysfinder
- Roderich Schuppremediation developer
- Mark Eslercoordinator
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;
exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;
if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
execFile("ping", ["-c", "1", host], onResult);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)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log (1)
- 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.