CVE-2023-22344
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 · uneditedUse of hard-coded credentials vulnerability in SS1 Ver.13.0.0.40 and earlier and Rakuraku PC Cloud Agent Ver.2.1.8 and earlier allows a remote attacker to obtain the password of the debug tool and execute it. As a result of exploiting this vulnerability with CVE-2023-22335 and CVE-2023-22336 vulnerabilities together, it may allow a remote attacker to execute an arbitrary code with SYSTEM privileges by sending a specially crafted script to the affected device.
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 confidenceThis vulnerability in SS1 and Rakuraku PC Cloud Agent involves hard-coded credentials that allow a remote attacker to obtain the password for a debug tool and execute it. When chained with CVE-2023-22335 and CVE-2023-22336, this enables remote arbitrary code execution with SYSTEM privileges through specially crafted scripts.
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<= 2.1.8<= 13.0.0.40CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SS1 or Rakuraku PC Cloud Agent is installedCheck installed programs list or look for SS1 or Rakuraku PC Cloud Agent executables on the systemAffected if Either product is found on the system
-
Determine the installed version of SS1Check the version information for SS1 (typically in program files or application properties) and compare to 13.0.0.40Affected if Version is 13.0.0.40 or lower
-
Determine the installed version of Rakuraku PC Cloud AgentCheck the version information for Rakuraku PC Cloud Agent (typically in program files or application properties) and compare to 2.1.8Affected if Version is 2.1.8 or lower
-
Locate debug tool componentsSearch for debug tool executables or related configuration files associated with SS1 or Rakuraku PC Cloud AgentAffected if Debug tool or related configuration files exist on the system with the hard-coded credential vulnerability
-
Verify if the debug tool is accessible or enabledCheck if the debug tool functionality is accessible or if credentials can be retrieved from configuration filesAffected if Debug tool is accessible or hard-coded credentials are present in configuration files
User is affected if either SS1 version 13.0.0.40 or lower, or Rakuraku PC Cloud Agent version 2.1.8 or lower is installed, and the debug tool with hard-coded credentials is present and accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to patched versions of SS1 (Ver.13.0.0.40+) and Rakuraku PC Cloud Agent (Ver.2.1.8+) and restrict network exposure to untrusted networks until patches are applied.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22344 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22344 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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