CVE-2022-23862 is a high severity local privilege escalation in Y Soft SAFEQ 6 Build 53, scored 7.8. Its JMX service on port 9696 required no authentication and ran as the Windows SYSTEM account. I could not confirm a fixed version from the sources, so ask Y Soft for the current build and restrict access to that port.
What's affected
The record names Y Soft SAFEQ 6, Build 53. It says the SafeQ JMX service listening on port 9696 is open to JMX MLet attacks, did not enforce authentication, and ran as NT Authority\System. Someone with access to the port could run code and become the system user.
The only public write-up linked from the record is the researcher's repository and PDF, plus the vendor's home page. There is no vendor advisory in the references, so I cannot state which build fixes the issue or whether other SAFEQ 6 builds are affected. Treat any SAFEQ 6 installation as potentially affected until Y Soft says otherwise.
The researcher states the one requirement is access to TCP port 9696. NVD records a local attack vector with low privileges and low complexity, which fits an attacker who already has a foothold on the server or a reachable network path to that port. The record's kev flag is false.
I am deliberately not describing the exploitation steps. The weakness is a missing authentication check on a management interface, and that is enough to act on.
Weakness class per the record: CWE-306.
How to check if you're exposed
Find every SAFEQ server and note the version and build from the product's admin console or installer details. Then check whether the JMX port is listening and who can reach it.
On the Windows server:
netstat -ano | findstr :9696
From another host that should not have access, test reachability with your normal network tools. If a machine that has no business talking to the print server can open that port, the exposure is real.
Check the service account too. The researcher's report says the service ran as SYSTEM, so a compromise of the service is a compromise of the host.
What to do now
- Inventory SAFEQ 6 servers and record version and build number.
- Contact Y Soft for the fixed build or a vendor statement on this CVE, and plan the upgrade.
- Block port 9696 at the host firewall except from systems that genuinely need it, and never expose it beyond the server.
- Where the vendor allows it, review whether the service really needs to run as SYSTEM, and enable authentication on management interfaces.
Why it matters
The weakness is missing authentication for a critical function (CWE-306). Java Management Extensions is a management interface that, when left open, lets a caller load and run code. Running that service as the highest privileged Windows account means whoever reaches it inherits that power.
Print management servers often hold credentials and sit on internal networks with wide reach. A local privilege escalation there can turn a low privileged foothold into control of the server, which is a useful stepping stone.
The general rule applies to any product: management ports should require authentication, bind only where needed and run with the least privilege the service can work with.
Quick check
Is there a confirmed fixed version?
Not in the sources I reviewed. The record references only the researcher's write-up and the vendor home page, so ask Y Soft for the fixed build.
Sources
Last reviewed: 19 October 2026.