CVE-2024-37124

Local arbitrary property-file creation

Published Jun 19, 2024 · Updated Aug 2, 2024

Arbitrary file creation in Ricoh Streamline NX PC Client allows local users to write property files anywhere on an affected Windows PC. Ricoh identifies a potentially dangerous function as the cause but has not disclosed the function, its input path, or its destination-path handling. No product account or user interaction is required once an attacker can execute locally; exploitation creates a property file at an attacker-chosen location.

CVSS severity4.0
Medium
EPSS probability0.51%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Arbitrary file creation in Ricoh Streamline NX PC Client allows local users to write property files anywhere on an affected Windows PC. Ricoh identifies a potentially dangerous function as the cause but has not disclosed the function, its input path, or its destination-path handling. No product account or user interaction is required once an attacker can execute locally; exploitation creates a property file at an attacker-chosen location.

The record

CVE
CVE-2024-37124
Published
Jun 19, 2024
Updated
Aug 2, 2024
Vendor
Ricoh Company, Ltd.
Product
RICOH Streamline NX PC Client
Classifications
CWE-94, CWE-676
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 19, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=and ver.3.6.2.1
  2. Affected versionversion=ver.3.2.1.19
  3. Affected versionversion=ver.3.3.1.3
  4. Affected versionversion=ver.3.3.2.201
  5. Affected versionversion=ver.3.4.3.1
  6. Affected versionversion=ver.3.5.1.201 (ver.3.5.1.200op1)
  7. Affected versionversion=ver.3.5.1.201\/ver.3.5.1.200op1\/
  8. Affected versionversion=ver.3.6.100.53
  9. Affected versionversion=ver.3.6.2.1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Ricoh Company, Ltd. · RICOH Streamline NX PC Clientversion=and ver.3.6.2.1; version=ver.3.2.1.19; version=ver.3.3.1.3; version=ver.3.3.2.201; version=ver.3.4.3.1; version=ver.3.5.1.201 (ver.3.5.1.200op1); version=ver.3.5.1.201\/ver.3.5.1.200op1\/; version=ver.3.6.100.53; version=ver.3.6.2.1

Published CVSS scores

4.0JPCERT/CC and IPACVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
9.8CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-94Improper Control of Generation of Code ('Code Injection')
CWE-676Use of Potentially Dangerous Function

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo