{"document":{"aggregate_severity":{"namespace":"https://www.suse.com/support/security/rating/","text":"low"},"category":"csaf_vex","csaf_version":"2.0","distribution":{"text":"Copyright 2024 SUSE LLC. All rights reserved.","tlp":{"label":"WHITE","url":"https://www.first.org/tlp/"}},"lang":"en","notes":[{"category":"summary","text":"SUSE CVE-2023-43123","title":"Title"},{"category":"description","text":"On unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems.\n\nThe method File.createTempFile on unix-like systems creates a file with predefined name (so easily identifiable) and by default will create this file with the permissions -rw-r--r--. Thus, if sensitive information is written to this file, other local users can read this information.\n\nFile.createTempFile(String, String) will create a temporary file in the system temporary directory if the 'java.io.tmpdir' system property is not explicitly set. \n\nThis affects the class   https://github.com/apache/storm/blob/master/storm-core/src/jvm/org/apache/storm/utils/TopologySpoutLag.java#L99   and was introduced by   https://issues.apache.org/jira/browse/STORM-3123 \n\nIn practice, this has a very limited impact as this class is used only if  ui.disable.spout.lag.monitoring\n\n is set to false, but its value is true by default.\nMoreover, the temporary file gets deleted soon after its creation.\n\nThe solution is to use   Files.createTempFile https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/nio/file/Files.html#createTempFile(java.lang.String,java.lang.String,java.nio.file.attribute.FileAttribute...)   instead.\n\nWe recommend that all users upgrade to the latest version of Apache Storm.","title":"Description of the CVE"},{"category":"legal_disclaimer","text":"CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).","title":"Terms of use"}],"publisher":{"category":"vendor","contact_details":"https://www.suse.com/support/security/contact/","name":"SUSE Product Security Team","namespace":"https://www.suse.com/"},"references":[{"category":"external","summary":"CVE-2023-43123","url":"https://www.suse.com/security/cve/CVE-2023-43123"},{"category":"external","summary":"SUSE Security Ratings","url":"https://www.suse.com/support/security/rating/"},{"category":"external","summary":"SUSE Bug 1217474 for CVE-2023-43123","url":"https://bugzilla.suse.com/1217474"}],"title":"SUSE CVE CVE-2023-43123","tracking":{"current_release_date":"2025-12-19T01:19:55Z","generator":{"date":"2025-02-14T06:13:35Z","engine":{"name":"cve-database.git:bin/generate-csaf-vex.pl","version":"1"}},"id":"CVE-2023-43123","initial_release_date":"2025-02-14T06:13:35Z","revision_history":[{"date":"2025-02-14T06:13:35Z","number":"2","summary":"Current version"},{"date":"2025-02-16T06:06:39Z","number":"3","summary":"Current version"},{"date":"2025-07-07T23:50:22Z","number":"4","summary":"Current version"},{"date":"2025-12-17T01:10:53Z","number":"5","summary":"description changed"},{"date":"2025-12-19T01:19:55Z","number":"6","summary":"description changed"}],"status":"interim","version":"6"}}}