Arbitrary code execution via insecure temporary files
Published Jun 25, 2021 · Updated Aug 3, 2024
Insecure temporary files in Avaya Aura Device Services 7.0.0 through 8.1.4.0 allow local users to execute arbitrary code. The vendor maps the flaw to temporary files created with insecure permissions but does not identify the affected file or script-handling function. A local account must supply a specially crafted script; successful exploitation runs attacker-controlled code in an undisclosed service context.
Summary
What happened
Insecure temporary files in Avaya Aura Device Services 7.0.0 through 8.1.4.0 allow local users to execute arbitrary code. The vendor maps the flaw to temporary files created with insecure permissions but does not identify the affected file or script-handling function. A local account must supply a specially crafted script; successful exploitation runs attacker-controlled code in an undisclosed service context.
The record
- CVE
- CVE-2021-25654
- Published
- Jun 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Avaya
- Product
- Avaya Aura Device Services
- Classifications
- CWE-378, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=7.0.0 <=8.1.4.0
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