CVSS 3.1
3.3 lowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NLow (3.3) in mpxj mpxj. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in net.sf.mpxj:mpxj 10.14.1.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:Nnet.sf.mpxj:mpxj (Maven): fixed in 10.14.1net.sf.mpxj (NuGet): fixed in 10.14.1net.sf.mpxj-for-csharp (NuGet): fixed in 10.14.1net.sf.mpxj-for-vb (NuGet): fixed in 10.14.1mpxj (PyPI): fixed in 10.14.1Explain CVE-2022-41954 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-41954?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-41954?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-41954 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| mpxj:mpxj | before 10.14.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-jf2p-4gqj-849g | Maven | net.sf.mpxj:mpxj | <10.14.1 | 10.14.1 |
| GHSA-jf2p-4gqj-849g | NuGet | net.sf.mpxj | <10.14.1 | 10.14.1 |
| GHSA-jf2p-4gqj-849g | NuGet | net.sf.mpxj-for-csharp | <10.14.1 | 10.14.1 |
| GHSA-jf2p-4gqj-849g | NuGet | net.sf.mpxj-for-vb | <10.14.1 | 10.14.1 |
| GHSA-jf2p-4gqj-849g | PyPI | mpxj | <10.14.1 | 10.14.1 |
| PYSEC-2022-42996 | PyPI | mpxj | <10.14.1 | 10.14.1 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).