CVE-2022-41954

Temporary File Information Disclosure vulnerability in MPXJ

Workarounds

Setting java.io.tmpdir to a directory to which only the user running the application has access will prevent other users from accessing these temporary files.

For more information

If you have any questions or comments about this advisory

• Open an issue in https://github.com/joniles/mpxj

On Unix-like operating systems (not Windows or macos), MPXJ's use of File.createTempFile(..) results in temporary files being created with the permissions -rw-r--r--. This means that any other user on the system can read the contents of this file. When MPXJ is reading a type of schedule file which requires the creation of a temporary file or directory, a knowledgeable local user could locate these transient files while they are in use and would then be able to read the schedule being processed by MPXJ.

CVE-2022-41954 has a CVSS score of 2.8 (Low). The vector is requires local access, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (10.14.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been patched, MPXJ version 10.14.1 and later includes the necessary changes.

1. What is CVE-2022-41954? CVE-2022-41954 is a low-severity security vulnerability in net.sf.mpxj:mpxj (maven), affecting versions < 10.14.1. It is fixed in 10.14.1.
2. How severe is CVE-2022-41954? CVE-2022-41954 has a CVSS score of 2.8 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-41954?
   • net.sf.mpxj:mpxj (maven) (versions < 10.14.1)
   • net.sf.mpxj (nuget) (versions < 10.14.1)
   • net.sf.mpxj-for-csharp (nuget) (versions < 10.14.1)
   • net.sf.mpxj-for-vb (nuget) (versions < 10.14.1)
   • mpxj (pip) (versions < 10.14.1)
4. Is there a fix for CVE-2022-41954? Yes. CVE-2022-41954 is fixed in 10.14.1. Upgrade to this version or later.
5. Is CVE-2022-41954 exploitable, and should I be worried? Whether CVE-2022-41954 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-41954 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-41954?
   • Upgrade net.sf.mpxj:mpxj to 10.14.1 or later
   • Upgrade net.sf.mpxj to 10.14.1 or later
   • Upgrade net.sf.mpxj-for-csharp to 10.14.1 or later
   • Upgrade net.sf.mpxj-for-vb to 10.14.1 or later
   • Upgrade mpxj to 10.14.1 or later

Other vulnerabilities in net.sf.mpxj:mpxj