SYSTEM code execution via unauthenticated JMX MLet
Published Oct 22, 2024 · Updated Oct 22, 2024
Missing authentication in the JMX service of YSoft SafeQ 6 Build 53 allows local users to execute arbitrary code as Windows SYSTEM. The service accepts unauthenticated JMX connections on TCP port 9696 and permits MLet loading while it runs under the NT Authority\System account. Access to port 9696 is required; successful exploitation grants full control of the affected Windows server.
Summary
What happened
Missing authentication in the JMX service of YSoft SafeQ 6 Build 53 allows local users to execute arbitrary code as Windows SYSTEM. The service accepts unauthenticated JMX connections on TCP port 9696 and permits MLet loading while it runs under the NT Authority\System account. Access to port 9696 is required; successful exploitation grants full control of the affected Windows server.
The record
- CVE
- CVE-2022-23862
- Published
- Oct 22, 2024
- Updated
- Oct 22, 2024
- Vendor
- Y Soft
- Product
- YSoft SafeQ 6
- Classifications
- CWE-306, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 22, 2024CVE publishedPublication date reported by the CVE source.
- Oct 22, 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=6_build_53
What conditions does exploitation require?
What is affected?
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
- CVE-2022-23862 JMX MLet proof of conceptproof 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