Unauthenticated AS2 message injection via Content-Type bypass
Published Jun 18, 2021 · Updated Aug 3, 2024
Authentication bypass in Cleo LexiCom 5.5.0.0 allows remote attackers to submit AS2 messages without sender authentication. The AS2 message handler accepts a text/plain Content-Type without enforcing the encryption and signature checks used to identify the sender. Network access to the AS2 receiver is sufficient, permitting an untrusted sender to inject messages that LexiCom accepts as inbound AS2 traffic.
Summary
What happened
Authentication bypass in Cleo LexiCom 5.5.0.0 allows remote attackers to submit AS2 messages without sender authentication. The AS2 message handler accepts a text/plain Content-Type without enforcing the encryption and signature checks used to identify the sender. Network access to the AS2 receiver is sufficient, permitting an untrusted sender to inject messages that LexiCom accepts as inbound AS2 traffic.
The record
- CVE
- CVE-2021-33577
- Published
- Jun 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 18, 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?
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
No sourced classifications are available.
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