Code execution via unvalidated project-file deserialization
Published May 10, 2024 · Updated Aug 1, 2024
Deserialization in NI FlexLogger and InstrumentStudio 2024 Q1 and earlier allows remote attackers to execute code via a crafted project file. The shared project-file parser accepts user-supplied content without sufficient validation and deserializes it inside the application process. A user must open the malicious project file; successful exploitation runs arbitrary code in the affected application's process context.
Summary
What happened
Deserialization in NI FlexLogger and InstrumentStudio 2024 Q1 and earlier allows remote attackers to execute code via a crafted project file. The shared project-file parser accepts user-supplied content without sufficient validation and deserializes it inside the application process. A user must open the malicious project file; successful exploitation runs arbitrary code in the affected application's process context.
The record
- CVE
- CVE-2024-4044
- Published
- May 10, 2024
- Updated
- Aug 1, 2024
- Vendor
- National Instruments
- Product
- InstrumentStudio
- Classifications
- CWE-502, CAPEC-586, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 10, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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.
- Affected versionversion=0 <=24.1
- Affected versionversion=2024 <=24.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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