CVE-2019-11364
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 · uneditedAn OS Command Injection vulnerability in Snare Central before 7.4.5 allows remote authenticated attackers to inject arbitrary OS commands via the ServerConf/DataManagement/DiskManager.php FORMNAS_share parameter.
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 confidenceOS Command Injection vulnerability in Snare Central's DiskManager.php allows authenticated remote attackers to execute arbitrary OS commands through the unvalidated FORMNAS_share parameter. This enables full system compromise of the server.
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< 7.4.5CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 Snare Central versionLocate the Snare Central installation and check the version file or application metadata. Common locations include the web application header/footer, a version info file in the installation directory, or the software's built-in about/status page.Affected if The installed version is any version prior to 7.4.5 (e.g., 7.4.0 through 7.4.4)
-
Verify DiskManager.php existsCheck if the file ServerConf/DataManagement/DiskManager.php exists in the Snare Central web root directory.Affected if The file DiskManager.php is present in the installation
-
Confirm endpoint accessibilityAttempt to access the DiskManager.php endpoint via HTTP/HTTPS request, or check web server configuration for routing to ServerConf/DataManagement/DiskManager.php.Affected if The endpoint is reachable over the network without being explicitly blocked by network-level access controls
-
Verify authentication configurationReview the authentication configuration for the DiskManager.php endpoint or the ServerConf/DataManagement area to confirm whether authentication is enforced, and assess the strength of the authentication mechanism.Affected if Authentication is disabled, weakly configured, or allows untrusted users to access the DiskManager.php functionality
You are affected if Snare Central version is below 7.4.5 AND the DiskManager.php endpoint is accessible to untrusted authenticated users.
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 data7.4.5
Upgrade Snare Central to version 7.4.5 or later to obtain the patched code. As a compensating control, restrict access to the ServerConf/DataManagement/DiskManager.php endpoint to only trusted authenticated users until the upgrade is 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-2019-11364 — 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-11364 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