Unauthenticated code execution via unrestricted file upload
Published Jan 9, 2020 · Updated Aug 6, 2024
Unrestricted file upload in BSS Continuity CMS 4.2.22640.0 allows remote attackers to execute arbitrary code without authentication. The public record does not identify the upload endpoint, accepted file types, storage path, or server-side validation failure. Network access to the CMS is sufficient; a successful upload permits code execution in the web server's security context.
Summary
What happened
Unrestricted file upload in BSS Continuity CMS 4.2.22640.0 allows remote attackers to execute arbitrary code without authentication. The public record does not identify the upload endpoint, accepted file types, storage path, or server-side validation failure. Network access to the CMS is sufficient; a successful upload permits code execution in the web server's security context.
The record
- CVE
- CVE-2014-3448
- Published
- Jan 9, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 9, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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
- BSS Continuity CMS 4.2.22640.0 Code Executionfunctional · unverified
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