Unauthenticated file-path discovery via internal request forgery
Published Apr 22, 2022 · Updated Sep 17, 2024
SSRF in Johnson Controls SCT and SCT Pro before 14.2.2 allows remote attackers to probe for files or paths through crafted requests. The affected request-processing locus is undisclosed; specially crafted input causes the product to forge an internal request and reveal whether a named file or path exists. No authentication or user interaction is required, and the disclosed consequence is limited to internal request forgery and file-or-path discovery.
Summary
What happened
SSRF in Johnson Controls SCT and SCT Pro before 14.2.2 allows remote attackers to probe for files or paths through crafted requests. The affected request-processing locus is undisclosed; specially crafted input causes the product to forge an internal request and reveal whether a named file or path exists. No authentication or user interaction is required, and the disclosed consequence is limited to internal request forgery and file-or-path discovery.
The record
- CVE
- CVE-2021-36203
- Published
- Apr 22, 2022
- Updated
- Sep 17, 2024
- Vendor
- Johnson Controls
- Product
- System Configuration Tool Pro (SCT Pro)
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2022CVE 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=All <14.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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