CVE-2019-0020
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 · uneditedJuniper ATP ships with hard coded credentials in the Web Collector instance which gives an attacker the ability to take full control of any installation of the software. Affected releases are Juniper Networks Juniper ATP: 5.0 versions prior to 5.0.3.
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 confidenceJuniper ATP ships with hardcoded credentials embedded in the Web Collector software component. Attackers who discover these credentials can authenticate to the Web Collector and gain full administrative control over the ATP installation, effectively compromising the entire threat prevention platform.
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.0.0, < 5.0.3CVSS 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.0/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.
-
Confirm Juniper ATP installationIdentify whether Juniper Advanced Threat Prevention software is deployed in your environment. This may be visible in your asset inventory, network security tools, or ATP management console.Affected if Juniper ATP is not installed in your environment
-
Check ATP version numberLocate the installed version of Juniper ATP through the management interface, system diagnostics, or version lookup command. Compare your version against the affected range: versions 5.0.0 through 5.0.2.Affected if Your ATP version is 5.0.0, 5.0.1, or 5.0.2 (any version >= 5.0.0 and < 5.0.3)
-
Verify Web Collector component statusCheck whether the Web Collector component is enabled or configured in your ATP installation. This may be visible in the ATP admin interface under collector settings or component status.Affected if Web Collector is enabled and your ATP version falls within the affected range 5.0.0-5.0.2
You are affected if Juniper ATP version 5.0.0, 5.0.1, or 5.0.2 is installed and the Web Collector component is enabled.
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.
dbcve · scoped5.0.3
Upgrade Juniper ATP to version 5.0.3 or later which removes the hardcoded credentials. This is a critical priority given the CVSS 9.8 score and trivial exploitability of hardcoded credentials.
Juniper ATP 5.0.3
- Backup the current Juniper ATP configuration before beginning the upgrade process
- Download Juniper ATP version 5.0.3 or later from the official Juniper Networks support portal (kb.juniper.net)
- Access the Juniper ATP admin interface or CLI
- Upload the 5.0.3 software image to the appliance
- Initiate the upgrade process following Juniper's standard upgrade procedures
- After upgrade completion, verify the installation was successful
- Confirm the hard-coded credentials vulnerability has been addressed by the upgrade
- Verify normal operation of the ATP system post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0020 — 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-0020 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