Authenticated firewall changes via missing permission metadata
Published Apr 30, 2021 · Updated Aug 3, 2024
Incorrect authorization in CubeCoders AMP 2.1.x before 2.1.1.2 allows remote authenticated users to open local firewall ports. The ADS port-management API endpoint lacks permission metadata, so it accepts crafted HTTP(S) requests from logged-in accounts without network-configuration rights. An ADS login is required, and the exposed operation adds custom firewall rules but cannot open ports below 1024.
Summary
What happened
Incorrect authorization in CubeCoders AMP 2.1.x before 2.1.1.2 allows remote authenticated users to open local firewall ports. The ADS port-management API endpoint lacks permission metadata, so it accepts crafted HTTP(S) requests from logged-in accounts without network-configuration rights. An ADS login is required, and the exposed operation adds custom firewall rules but cannot open ports below 1024.
The record
- CVE
- CVE-2021-31926
- Published
- Apr 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1562.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 30, 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
Public exploit references
- GitHub issue 443 reproductionproof of concept · demonstrated
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