pysec-2022-42996
Vulnerability from pysec
Published
2022-11-25 19:15
Modified
2023-05-04 04:29
Details

MPXJ is an open source library to read and write project plans from a variety of file formats and databases. 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 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. The problem has been patched, MPXJ version 10.14.1 and later includes the necessary changes. Users unable to upgrade may set 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.




{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "mpxj",
        "purl": "pkg:pypi/mpxj"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "287ad0234213c52b0638565e14bd9cf3ed44cedd"
            }
          ],
          "repo": "https://github.com/joniles/mpxj",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "10.14.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "10.0.0",
        "10.0.1",
        "10.0.2",
        "10.0.3",
        "10.0.4",
        "10.0.5",
        "10.1.0",
        "10.10.0",
        "10.11.0",
        "10.12.0",
        "10.13.0",
        "10.14.0",
        "10.2.0",
        "10.3.0",
        "10.4.0",
        "10.5.0",
        "10.6.0",
        "10.6.1",
        "10.6.2",
        "10.7.0",
        "10.8.0",
        "10.9.0",
        "10.9.1",
        "9.0.0",
        "9.1.0",
        "9.2.0",
        "9.2.1",
        "9.2.2",
        "9.2.3",
        "9.2.4",
        "9.2.5",
        "9.2.6",
        "9.3.0",
        "9.3.1",
        "9.4.0",
        "9.5.0",
        "9.5.1",
        "9.5.2",
        "9.6.0",
        "9.7.0",
        "9.8.0",
        "9.8.1",
        "9.8.2",
        "9.8.3"
      ]
    }
  ],
  "aliases": [
    "CVE-2022-41954",
    "GHSA-jf2p-4gqj-849g"
  ],
  "details": "MPXJ is an open source library to read and write project plans from a variety of file formats and databases. On 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 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. The problem has been patched, MPXJ version 10.14.1 and later includes the necessary changes. Users unable to upgrade may set `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.",
  "id": "PYSEC-2022-42996",
  "modified": "2023-05-04T04:29:27.436392Z",
  "published": "2022-11-25T19:15:00Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/joniles/mpxj/security/advisories/GHSA-jf2p-4gqj-849g"
    },
    {
      "type": "FIX",
      "url": "https://github.com/joniles/mpxj/commit/287ad0234213c52b0638565e14bd9cf3ed44cedd"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.