PaddlePaddle up to 2.3 paddle.audio.functional.get_window winstr code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in PaddlePaddle up to 2.3. The impacted element is the function paddle.audio.functional.get_window. The manipulation of the argument winstr leads to code injection.
This vulnerability is uniquely identified as CVE-2022-45908. No exploit exists.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in PaddlePaddle up to 2.3. It has been rated as critical. This issue affects the function paddle.audio.functional.get_window. The manipulation of the argument winstr with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In PaddlePaddle before 2.4, paddle.audio.functional.get_window is vulnerable to code injection because it calls eval on a user-supplied winstr. This may lead to arbitrary code execution.
The weakness was disclosed 11/26/2022 as pdsa-2022-002. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-45908 since 11/26/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
Upgrading to version 2.4 eliminates this vulnerability. Applying the patch 26c419ca386aeae3c461faf2b828d00b48e908eb is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: PaddlePaddle 2.4
Patch: 26c419ca386aeae3c461faf2b828d00b48e908eb
Timeline
11/26/2022 🔍11/26/2022 🔍
11/26/2022 🔍
04/26/2025 🔍
Sources
Advisory: pdsa-2022-002Status: Confirmed
CVE: CVE-2022-45908 (🔍)
GCVE (CVE): GCVE-0-2022-45908
GCVE (VulDB): GCVE-100-214397
Entry
Created: 11/26/2022 08:00Updated: 04/26/2025 04:05
Changes: 11/26/2022 08:00 (43), 12/23/2022 13:14 (11), 04/26/2025 04:05 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.