dbcve.org
Atok Medical 2Application · Justsystems

CVE-2022-36344

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An unquoted search path vulnerability exists in 'JustSystems JUST Online Update for J-License' bundled with multiple products for corporate users as in Ichitaro through Pro5 and others. Since the affected product starts another program with an unquoted file path, a malicious file may be executed with the privilege of the Windows service if it is placed in a certain path. Affected products are bundled with the following product series: Office and Office Integrated Software, ATOK, Hanako, JUST PDF, Shuriken, Homepage Builder, JUST School, JUST Smile Class, JUST Smile, JUST Frontier, JUST Jump, and Tri-De DetaProtect.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unquoted service path vulnerability exists in JustSystems JUST Online Update for J-License bundled with multiple Japanese office and utility software products. The service launches executables without quoting paths containing spaces, allowing attackers to place malicious executables in intermediate directories that get executed with SYSTEM-level privileges when the service starts.

MitigationApply vendor patches from JustSystems for all affected products; ensure strict file system permissions on service directories to prevent unauthorized executable placement.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Atok Medical 2Application
Affected:all versions
Atok Medical 3Application
Affected:all versions
Atok Pro 3Application
Affected:all versions
Atok Pro 4Application
Affected:all versions
Atok Pro 5Application
Affected:all versions
Hanako Police 5Application
Affected:all versions
Hanako Police 6Application
Affected:all versions
Hanako Police 7Application
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if affected JustSystems products are installed
    Check installed programs for any of: JustSystems Atok Medical 2/3, Atok Pro 3/4/5, Hanako Police 5/6/7. Use 'Programs and Features' in Control Panel or PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName | Where-Object {$_.DisplayName -match 'Atok|Hanako'}
    Affected if Any of the listed JustSystems products appear in installed programs
  2. Locate the JUST Online Update service
    Open Services (services.msc) and look for a service named 'JUST Online Update' or 'J-License' related service. Alternatively, run: Get-Service | Where-Object {$_.DisplayName -match 'JUST|J-License'}
    Affected if The JUST Online Update service is present on the system
  3. Check service binary path for unquoted spaces
    Run in PowerShell: Get-WmiObject win32_service | Where-Object {$_.DisplayName -match 'JUST|J-License'} | Select-Object Name, PathName. Examine the PathName field - if it contains spaces and is not enclosed in quotation marks, the vulnerability exists.
    Affected if The service PathName contains spaces and is not surrounded by quotes (e.g., C:\Program Files\JustSystems\... instead of "C:\Program Files\JustSystems\...")
  4. Verify write permissions on intermediate directories
    For the unquoted path (e.g., C:\Program Files\JustSystems\), check if standard users can write to any directory in the path hierarchy. Use icacls from command prompt: icacls "C:\Program Files\JustSystems"
    Affected if Users with low privileges can write to directories in the service executable path, allowing placement of malicious executables

If a JustSystems product from the list is installed AND the JUST Online Update service exists with an unquoted path containing spaces AND the intermediate directories are writable by non-admin users, the system is affected by CVE-2022-36344.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches from JustSystems for all affected products; ensure strict file system permissions on service directories to prevent unauthorized executable placement.

Fix this in Atok Medical 2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36344 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36344 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data