Arbitrary code execution via evaluated window name
Published Nov 26, 2022 · Updated Apr 25, 2025
Code injection in PaddlePaddle before 2.4 allows attackers to execute arbitrary code through a crafted audio-window name. The paddle.audio.functional.get_window function prefixes winstr with an underscore and passes the result to Python eval without restricting it to registered window functions. The affected application must pass attacker-controlled winstr data into the function, and execution occurs with the hosting process privileges.
Summary
What happened
Code injection in PaddlePaddle before 2.4 allows attackers to execute arbitrary code through a crafted audio-window name. The paddle.audio.functional.get_window function prefixes winstr with an underscore and passes the result to Python eval without restricting it to registered window functions. The affected application must pass attacker-controlled winstr data into the function, and execution occurs with the hosting process privileges.
The record
- CVE
- CVE-2022-45908
- Published
- Nov 26, 2022
- Updated
- Apr 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1059.006
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 25, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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