Unauthenticated endpoint access via proxy path traversal
Published Mar 18, 2022 · Updated Nov 20, 2024
Path traversal in Pascom Cloud Phone System before 7.20.x allows remote attackers to reach unintended Tomcat endpoints. An NGINX reverse-proxy rule treats /..;/ as a directory while Tomcat normalizes it as /../, letting requests escape the exposed servlet path. No authentication is required; the flaw exposes internal servlets and can be chained with separate SSRF and command-injection flaws for container-level code execution.
Summary
What happened
Path traversal in Pascom Cloud Phone System before 7.20.x allows remote attackers to reach unintended Tomcat endpoints. An NGINX reverse-proxy rule treats /..;/ as a directory while Tomcat normalizes it as /../, letting requests escape the exposed servlet path. No authentication is required; the flaw exposes internal servlets and can be chained with separate SSRF and command-injection flaws for container-level code execution.
The record
- CVE
- CVE-2021-45967
- Published
- Mar 18, 2022
- Updated
- Nov 20, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2022CVE publishedPublication date reported by the CVE source.
- Nov 20, 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
- NGINX-to-Tomcat /..;/ traversal requestfunctional · 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