Exported package decryption via hardcoded cryptographic key
Published Apr 29, 2022 · Updated Aug 3, 2024
Hardcoded-key exposure in Automation Anywhere Automation 360 22 allows attackers to decrypt exported RPA packages with the embedded key. The package-export encryption path uses a cryptographic key hardcoded in the product, allowing the same key to decrypt packages produced by version 22. Exploitation requires access to an exported RPA package and the embedded key; the documented consequence is disclosure of package contents.
Summary
What happened
Hardcoded-key exposure in Automation Anywhere Automation 360 22 allows attackers to decrypt exported RPA packages with the embedded key. The package-export encryption path uses a cryptographic key hardcoded in the product, allowing the same key to decrypt packages produced by version 22. Exploitation requires access to an exported RPA package and the embedded key; the documented consequence is disclosure of package contents.
The record
- CVE
- CVE-2022-29856
- Published
- Apr 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1140
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 2022CVE 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?
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