CVE-2019-19518
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 · uneditedCA Automic Sysload 5.6.0 through 6.1.2 contains a vulnerability, related to a lack of authentication on the File Server port, that potentially allows remote attackers to execute arbitrary commands.
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 confidenceCA Automic Sysload versions 5.6.0 through 6.1.2 contains a File Server component that listens on a network port without requiring authentication, allowing unauthenticated remote attackers to send commands that result in arbitrary command execution.
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>= 5.6.0, <= 6.1.2CVSS 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 if CA Automic Sysload is installedLook for Sysload installation directories or check installed software on the system. Common locations may include /opt/sysload or program files directories. Use system inventory tools if available.Affected if CA Automic Sysload software is found on the system
-
Determine the installed Sysload versionCheck the version of the installed CA Automic Sysload software. Look for version information in the installation directory, about dialogs, or use system commands to query the installed package.Affected if The installed version falls within the range 5.6.0 to 6.1.2 (inclusive)
-
Locate and verify the File Server componentIdentify whether the Sysload File Server component is present and running. This component typically runs as a service or daemon. Check for related processes or services.Affected if The File Server component is installed and running on the system
-
Identify the File Server network configurationExamine the File Server configuration to determine which network port it is listening on. Check configuration files or running network services to find the listening port.Affected if The File Server is listening on a network port and is accessible over the network
-
Verify authentication status on the File ServerReview the File Server configuration settings to determine whether authentication is required or if it is disabled. Look for authentication-related parameters in configuration files.Affected if Authentication is disabled or not required for the File Server, making it accessible without credentials
A system is affected if CA Automic Sysload version 5.6.0 through 6.1.2 is installed with the File Server component enabled and accessible over the network without authentication enforcement.
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 dataRestrict network access to the File Server port using firewall rules or network segmentation, and apply any available vendor patches. If authentication cannot be enforced, consider disabling the File Server if not required.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19518 — 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-19518 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