CVE-2019-19469
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 Zmanda Management Console 3.3.9, ZMC_Admin_Advanced?form=adminTasks&action=Apply&command= allows CSRF, as demonstrated by command injection with shell metacharacters. This may depend on weak default credentials.
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 confidenceThe Zmanda Management Console 3.3.9 contains a CSRF vulnerability in the ZMC_Admin_Advanced form that allows attackers to inject arbitrary shell commands via the Apply action with shell metacharacters. Successful exploitation can lead to command execution on the host system.
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= 3.3.9CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Zmanda Management Console installation and versionLook for Zmanda Amanda installation. Check for the ZMC (Zmanda Management Console) binary or web interface. On Linux systems, check for /opt/zmanda/amanda/bin/zmc or similar paths, or the ZMC web service typically on port 8008/8009. Use 'rpm -q zmandaclient' or 'dpkg -l | grep zmand' on Linux, or check Windows Programs and Features for Zmanda Amanda.Affected if The installed version is exactly 3.3.9 (the only affected version per this CVE)
-
Confirm ZMC web interface is accessibleCheck if the Zmanda Management Console web interface is running and accessible on the server. This is typically served on ports 8008 or 8009. Verify the service is listening with 'netstat -tlnp | grep -E "8008|8009"' or similar port check.Affected if The ZMC web interface is accessible and the version is 3.3.9
-
Verify admin interface is reachableNavigate to or check for the ZMC_Admin_Advanced form within the Zmanda Management Console. This is typically found under Admin or Advanced settings in the ZMC web interface. Check for the presence of 'ZMC_Admin_Advanced' in web application files or accessible URLs.Affected if The ZMC_Admin_Advanced form is accessible without CSRF protection in version 3.3.9
-
Check for CSRF token implementationInspect the ZMC_Admin_Advanced form submission behavior. Submit a request to the Apply action and examine whether a valid CSRF token or anti-CSRF mechanism is required. If the form can be submitted from a cross-site request without token validation, the vulnerability is present.Affected if The Apply action in ZMC_Admin_Advanced form does not require valid CSRF tokens and accepts shell metacharacters in parameters
A system is affected if Zmanda Management Console version 3.3.9 is installed, the ZMC web interface is accessible, and the ZMC_Admin_Advanced form allows CSRF-protected submissions without anti-CSRF tokens and accepts shell metacharacters in the Apply action.
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 dataImplement anti-CSRF tokens for state-changing operations, enforce strong unique credentials to replace defaults, and apply strict input validation/sanitization to prevent command injection in the admin interface.
- Consultation6.0 h
- Implementation12.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19469 — 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-19469 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