CVE-2019-13157
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 · uneditednsGreen.dll in Naver Vaccine 2.1.4 allows remote attackers to overwrite arbitary files via directory traversal sequences in a filename within nsz archive.
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 confidenceA directory traversal vulnerability exists in nsGreen.dll of Naver Vaccine 2.1.4 when processing nsz archive files. The DLL fails to properly sanitize filenames containing traversal sequences (e.g., '../'), allowing attackers to write files to arbitrary filesystem locations, potentially achieving code execution or privilege escalation.
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.4CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Check if Naver Vaccine is installedLook for Naver Vaccine in the installed programs list (Control Panel > Programs and Features) or search for the executable/named folder on the systemAffected if Naver Vaccine is present on the system
-
Verify the installed version is 2.1.4Right-click on the Naver Vaccine application or its executable, select Properties, and check the Version tab. Alternatively, open the application and look in Help > AboutAffected if The version is exactly 2.1.4
-
Confirm the vulnerable DLL existsLocate nsGreen.dll in the Naver Vaccine installation directory, typically found in the program folder (e.g., C:\Program Files\Naver Vaccine\)Affected if nsGreen.dll is present in the Naver Vaccine installation folder
-
Check for nsz archive processing activityLook for any recently opened or processed .nsz files on the system, or check the application's file association settings for nsz filesAffected if The system has been used to open or process nsz archive files using Naver Vaccine 2.1.4
A system is affected only if Naver Vaccine version 2.1.4 is installed and has been used to process nsz archive files, which triggers the vulnerable code path in nsGreen.dll.
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 dataUpdate Naver Vaccine to a patched version that properly validates and sanitizes file paths within nsz archives. Until patched, avoid opening nsz files from untrusted sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13157 — 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-2019-13157 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