Code execution via malformed BCP project parsing
Published Jun 25, 2021 · Updated Sep 17, 2024
Memory corruption in Phoenix Contact Automation Worx Software Suite 1.87 and earlier allows attackers to execute code via a crafted BCP file. The BCP parser frees unallocated memory because project data is incompletely initialized and inadequately validated. Exploitation requires access to an original bus configuration file, replacement of that file on the engineering workstation, and user interaction; deployed automation systems are unaffected.
Summary
What happened
Memory corruption in Phoenix Contact Automation Worx Software Suite 1.87 and earlier allows attackers to execute code via a crafted BCP file. The BCP parser frees unallocated memory because project data is incompletely initialized and inadequately validated. Exploitation requires access to an original bus configuration file, replacement of that file on the engineering workstation, and user interaction; deployed automation systems are unaffected.
The record
- CVE
- CVE-2021-33542
- Published
- Jun 25, 2021
- Updated
- Sep 17, 2024
- Vendor
- Phoenix Contact
- Product
- Automation Worx Software Suite
- Classifications
- CWE-824, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=Config+ <=1.87
- Affected versionversion=PC Worx <=1.87
- Affected versionversion=PC Worx Express <=1.87
What conditions does exploitation require?
What is affected?
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