# CVE-2023-43123: Apache Storm: Local Information Disclosure Vulnerability in Storm-core on Unix-Like systems due temporary files > Local attackers can read sensitive data from temporary files in Apache Storm if spout lag monitoring is enabled, which is disabled by default. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Nov 2023 - **Updated:** 13 Feb 2025 - **Also known as:** GHSA-85p4-q357-72h9 ## What is CVE-2023-43123? CVE-2023-43123 is a medium-severity vulnerability in Apache Storm, published on 23 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. The 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. File.createTempFile(String, String) will create a temporary file in the system temporary directory if the 'java.io.tmpdir' system property is not explicitly set. This 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 In practice, this has a very limited impact as this class is used only if ui.disable.spout.lag.monitoring is set to false, but its value is true by default. Moreover, the temporary file gets deleted soon after its creation. The 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. We recommend that all users upgrade to the latest version of Apache Storm. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2023-43123? 2 open source packages ship an affected version, including org.apache.storm:storm-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.storm:storm-core` | Maven | From 2.0.0 | 2.6.0 | | `org.apache.storm:storm-core` | Maven | From 2.0.0 | 2.6.0 | Products: Apache Storm. ## How do I fix CVE-2023-43123? Upgrade org.apache.storm:storm-core to 2.6.0 or later. ## Is CVE-2023-43123 being exploited? There is no known exploitation of CVE-2023-43123 in the wild and no public exploit code. ## Other vulnerabilities in Apache Storm - [CVE-2021-38294](https://insights.sbomify.com/CVE-2021-38294/): Shell Command Injection Vulnerability in Nimbus Thrift Server (critical 9.8) - [CVE-2021-40865](https://insights.sbomify.com/CVE-2021-40865/): Unsafe Pre-Authentication Deserialization In Workers (critical 9.8) - [CVE-2018-11779](https://insights.sbomify.com/CVE-2018-11779/): Deserialization of Untrusted Data in Apache Storm (critical 9.8) - [CVE-2015-3188](https://insights.sbomify.com/CVE-2015-3188/): Apache Storm remote code execution vulnerability (critical 9.8) - [CVE-2026-35337](https://insights.sbomify.com/CVE-2026-35337/): Apache Storm Client: RCE through Unsafe Deserialization via Kerberos TGT Credential Handling (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-43123 and fix it if it is affected. What it is: CVE-2023-43123 is a medium-severity vulnerability in Apache Storm, published on 23 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-43123 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.storm:storm-core (Maven): affected from 2.0.0; fixed in 2.6.0 - org.apache.storm:storm-core (Maven): affected from 2.0.0; fixed in 2.6.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-43123/ (Markdown: https://insights.sbomify.com/CVE-2023-43123/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-43123 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-43123 - OSV: https://osv.dev/vulnerability/CVE-2023-43123 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-43123/ Summaries are generated and may contain mistakes; the official description above is the record.