Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact When reading a suitably crafted PRX or STX file, MPXJ can be made to write files to arbitrary locations in the file system. Patches This issue is addressed in MPXJ version 16.5.0. Workarounds Do not read PRX or STX files from untrusted sources.
Recommended action: Upgrade to 16.5.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact MPXJ used the default configuration when creating a DocumentBuilder instance, which leaves doctype declarations enabled, when parsing the XML content of the ZTIMEINTERVALS column from a Merlin project SQLite file. This would allow a carefully crafted XML payload to read an arbitrary file. However, although an arbitrary file can be read, the way the resulting parsed XML is processed by MPXJ means that the data it contains is unlikely to be available for exfiltration. Patches The patch is included in MPXJ 16.4.1 Workarounds Potential workarounds include: Avoid reading Merlin project files with MPXJ Only accept Merlin project files from trusted sources Preprocess Merlin SQLite databases to strip doctype declarations from the ZTIMEINTERVALS column
Recommended action: Upgrade to 16.4.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact The patch for the historical vulnerability CVE-2020-35460 in MPXJ is incomplete as there is still a possibility that a malicious path could be constructed which would not be picked up by the original fix and allow files to be written to arbitrary locations. Patches The issue is addressed in MPXJ version 13.5.1 Workarounds Do not pass zip files to MPXJ. References N/A Credits Issue report and patch provided by yyjLF and sprinkle
Recommended action: Upgrade to 13.5.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact 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. Patches The problem has been patched, MPXJ version 10.14.1 and later includes the necessary changes. 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
Recommended action: Upgrade to 10.14.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.