ghsa-jf2p-4gqj-849g
Vulnerability from github
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
{ "affected": [ { "package": { "ecosystem": "Maven", "name": "net.sf.mpxj:mpxj" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "10.14.1" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "NuGet", "name": "net.sf.mpxj" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "10.14.1" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "NuGet", "name": "net.sf.mpxj-for-csharp" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "10.14.1" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "NuGet", "name": "net.sf.mpxj-for-vb" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "10.14.1" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "PyPI", "name": "mpxj" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "10.14.1" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2022-41954" ], "database_specific": { "cwe_ids": [ "CWE-200", "CWE-668" ], "github_reviewed": true, "github_reviewed_at": "2022-11-28T22:09:09Z", "nvd_published_at": "2022-11-25T19:15:00Z", "severity": "LOW" }, "details": "### Impact\nOn Unix-like operating systems (not Windows or macos), MPXJ\u0027s 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.\n\n### Patches\nThe problem has been patched, MPXJ version 10.14.1 and later includes the necessary changes.\n\n### Workarounds\nSetting `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.\n\n### For more information\nIf you have any questions or comments about this advisory\n* Open an issue in https://github.com/joniles/mpxj\n", "id": "GHSA-jf2p-4gqj-849g", "modified": "2024-09-26T14:24:09Z", "published": "2022-11-28T22:09:09Z", "references": [ { "type": "WEB", "url": "https://github.com/joniles/mpxj/security/advisories/GHSA-jf2p-4gqj-849g" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-41954" }, { "type": "WEB", "url": "https://github.com/joniles/mpxj/commit/287ad0234213c52b0638565e14bd9cf3ed44cedd" }, { "type": "WEB", "url": "https://github.com/joniles/mpxj/commit/ae0af24345d79ad45705265d9927fe55e94a5721" }, { "type": "PACKAGE", "url": "https://github.com/joniles/mpxj" }, { "type": "WEB", "url": "https://github.com/pypa/advisory-database/tree/main/vulns/mpxj/PYSEC-2022-42996.yaml" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N", "type": "CVSS_V3" }, { "score": "CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N", "type": "CVSS_V4" } ], "summary": "Temporary File Information Disclosure vulnerability in MPXJ" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.