Protected-subnet access via routed port-security bypass
Published Feb 18, 2020 · Updated Aug 5, 2024
Improper access control in Phoenix Contact FL NAT 2208 and 2304-2GC-2SFP firmware before 2.90 allows adjacent attackers to reach protected subnets. The routing path forwards traffic from a device rejected by MAC-based or 802.1X port security into another subnet instead of enforcing the ingress port's authorization decision. Exploitation requires access to the local network segment and inter-subnet routing; it permits traffic into the protected subnet but not access to the authorized peer device.
Summary
What happened
Improper access control in Phoenix Contact FL NAT 2208 and 2304-2GC-2SFP firmware before 2.90 allows adjacent attackers to reach protected subnets. The routing path forwards traffic from a device rejected by MAC-based or 802.1X port security into another subnet instead of enforcing the ingress port's authorization decision. Exploitation requires access to the local network segment and inter-subnet routing; it permits traffic into the protected subnet but not access to the authorized peer device.
The record
- CVE
- CVE-2019-18352
- Published
- Feb 18, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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