CVE-2020-5555
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 · uneditedShihonkanri Plus GOOUT Ver1.5.8 and Ver2.2.10 allows remote attackers to read and write data of the files placed in the same directory where it is placed via unspecified vector due to the improper input validation issue.
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 · moderate confidenceShihonkanri Plus GOOUT versions 1.5.8 and 2.2.10 contain an improper input validation vulnerability that allows remote attackers to read and write files in the same directory as the application installation. This appears to be a directory traversal or file inclusion issue where user-supplied input is not adequately validated before being used in file operations.
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= 1.5.8= 2.2.10CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 installed version of Shihonkanri Plus GOOUTLocate the application version information in the software itself, about dialog, installation directory, or system inventory records. Compare against the affected versions 1.5.8 and 2.2.10.Affected if The installed version is exactly 1.5.8 or 2.2.10
-
Determine if web-facing file operations are enabledReview the application configuration or feature settings to confirm whether file upload, download, import, export, or attachment functionalities are accessible to users.Affected if File operation features such as file upload, download, or file browsing are enabled and accessible to users
-
Inspect file operation parameters for lack of validationExamine application logs, request parameters, or any accessible code snippets that handle file paths. Look for parameters that accept filenames or paths without sanitization checks.Affected if User-supplied input for file paths appears in requests without evident validation or sanitization mechanisms
-
Check for directory traversal exposure in file handlingTest or review file operation endpoints by providing path traversal sequences such as ../ in file request parameters. Observe whether the application allows access outside the intended directory.Affected if The application allows reading or writing files outside the intended application directory when traversal sequences are provided
You are affected if your installed version is 1.5.8 or 2.2.10 and file operation features are enabled and exposed without proper input validation on file path parameters.
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 a patched version of Shihonkanri Plus GOOUT. Until then, implement strict input validation on all file operation parameters and restrict file system permissions to limit exposure.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5555 — 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-2020-5555 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