CVE-2019-15131
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 · uneditedIn Code42 Enterprise 6.7.5 and earlier, 6.8.4 through 6.8.8, and 7.0.0 a vulnerability has been identified that may allow arbitrary files to be uploaded to Code42 servers and executed. This vulnerability could allow an attacker to create directories and save files on Code42 servers, which could potentially lead to code execution.
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 confidenceAn unrestricted file upload vulnerability in Code42 Enterprise allows attackers to create directories and save arbitrary files on the server, potentially leading to remote code execution. The vulnerability affects versions 6.7.5 and earlier, 6.8.4-6.8.8, and 7.0.0.
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<= 6.7.5>= 6.8.4, <= 6.8.8= 7.0.0CVSS 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 installed Code42 versionAccess the Code42 administration console or use the system's package manager or version lookup command to determine the exact version of Code42 Enterprise installedAffected if The installed version is 6.7.5 or earlier, between 6.8.4 and 6.8.8 inclusive, or exactly 7.0.0
-
Confirm web interface exposureDetermine if the Code42 web console is accessible from untrusted networks or the internet by reviewing network firewall rules and reverse proxy configurationsAffected if The administrative web interface is exposed to untrusted users without proper network segmentation or authentication barriers
-
Review upload functionality statusCheck the Code42 configuration settings or documentation to determine if file upload features are enabled for usersAffected if File upload functionality is enabled and accessible to users or unauthenticated actors
-
Audit server file system for unexpected artifactsExamine the Code42 server file system for newly created directories or files in upload directories that do not correspond to legitimate backup or sync operationsAffected if Unexpected directories or executable files are found in storage locations not created by authorized administrators
-
Analyze access logs for upload anomaliesReview Code42 server access logs and web server logs for unusual upload requests, particularly those creating directories or uploading files with executable extensionsAffected if Log entries show unauthorized directory creation or file uploads, especially from unauthenticated sources
A system is affected if it runs a Code42 version in the affected ranges AND has the web interface or file upload functionality exposed to potential attackers, or if evidence of unauthorized file uploads is found on the server.
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 dataApply available patches or upgrade to a supported version that addresses this vulnerability; if no patch is available, disable or restrict file upload functionality and monitor for suspicious upload activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15131 — 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-15131 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