dbcve.org
StormApplication · Apache

CVE-2023-43123

MEDIUM · 5.5 CVSS v3.1 Published 2023-11-23
Fix available
A fix is available. Upgrade to 2.6.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Storm's TopologySpoutLag class uses File.createTempFile which creates temporary files with permissions -rw-r--r-- on Unix-like systems, allowing other local users to read sensitive information written to these files. The vulnerability exists because the default Java temp file permissions are too permissive.

MitigationUpgrade to the latest version of Apache Storm or replace File.createTempFile with Files.createTempFile using appropriate FileAttribute parameters to restrict file permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StormApplication
Affected:>= 2.0.0, < 2.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Storm installation and version
    Run 'storm version' or check the Storm installation directory for version info. Common paths: /opt/storm, /usr/local/storm, or check via package manager.
    Affected if Version is 2.0.0 or higher but lower than 2.6.0
  2. Locate the TopologySpoutLag class
    Search for 'TopologySpoutLag' in Storm's jar files or source code. Common location: storm-core/src/java/org/apache/storm/daemon/TopologySpoutLag.java
    Affected if The vulnerable class exists in the installed version (present in 2.0.0-2.5.x)
  3. Determine if TopologySpoutLag is used in any topology
    Search topology definitions or logs for references to TopologySpoutLag. Check if any bolt or spout logs reference lag calculations or this class.
    Affected if The topology actively uses features that invoke TopologySpopLag functionality (such as spout lag metrics)
  4. Check for multi-user environment
    List system users with 'getent passwd' or 'cat /etc/passwd'. Check if Storm runs as a different user than other local users.
    Affected if Multiple local users exist on the system and Storm runs as a non-root user with readable temp directories
  5. Inspect temp file permissions
    When Storm runs, examine files in the system temp directory (usually /tmp). Look for files created by the Storm process with permissions -rw-r--r--.
    Affected if Temp files created by Storm are readable by other local users (permissions show 'r--r--r--' for group/other)

You are affected if Apache Storm version is between 2.0.0 and 2.5.x inclusive, TopologySpoutLag functionality is used in your topologies, and the system has other local users who could read the world-readable temp files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.0 or later
Fixed in 2.6.0
Interim mitigation

Upgrade to the latest version of Apache Storm or replace File.createTempFile with Files.createTempFile using appropriate FileAttribute parameters to restrict file permissions.

Recommended fix High confidence

2.6.0

  1. Upgrade Apache Storm to version 2.6.0 or later to include the fix that replaces File.createTempFile with Files.createTempFile

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Storm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-43123 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-43123 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data