Junos SpaceApplication · Juniper

CVE-2021-0220

MEDIUM · 6.8 CVSS v3.1 Published 2021-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
The Junos Space Network Management Platform has been found to store shared secrets in a recoverable format that can be exposed through the UI. An attacker who is able to execute arbitrary code in the victim browser (for example via XSS) or access cached contents may be able to obtain a copy of credentials managed by Junos Space. The impact of a successful attack includes, but is not limited to, obtaining access to other servers connected to the Junos Space Management Platform. This issue affects Juniper Networks Junos Space versions prior to 20.3R1.

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 confidence

Junos Space Network Management Platform stores shared secrets (credentials for managed devices and users) in a recoverable format that can be retrieved through the web UI. An attacker who can execute JavaScript in a victim's browser (via XSS) or access cached browser contents can extract these credentials, potentially gaining access to other servers connected to the Junos Space platform.

MitigationUpgrade Junos Space to version 20.3R1 or later, which implements proper secure credential storage (non-reversible hashing). Additionally, mitigate XSS vulnerabilities and clear browser caches as a defense-in-depth measure.

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
Junos SpaceApplication
Affected:= 1.0= 1.1= 1.2= 1.3= 1.4= 2.0= 11.1= 11.2= 11.3= 11.4= 12.1= 12.2

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Junos Space version
    Access the web UI login page or check the system via CLI: log into the Junos Space appliance and run 'show version' or check the About page in the web UI to display the installed version number
    Affected if The displayed version matches any of these: 1.0, 1.1, 1.2, 1.3, 1.4, 2.0, 11.1, 11.2, 11.3, 11.4, 12.1, or 12.2
  2. Confirm web UI is accessible
    Verify that the Junos Space web interface is reachable over HTTPS/HTTP by attempting to access the login URL (typically https://<hostname>/)
    Affected if The web UI login page loads and accepts authentication requests
  3. Check for stored device credentials
    Log into Junos Space web UI as an administrator and navigate to the Device Management or Credentials section to view managed devices and their stored authentication credentials
    Affected if Managed devices exist with stored usernames and passwords that are viewable in plain text or recoverable format through the UI
  4. Verify credential recoverability
    Within the web UI, attempt to retrieve or export stored credentials for any managed device or user account - observe whether the original password or a recoverable representation is displayed
    Affected if Stored credentials can be retrieved, viewed, or exported in plaintext or any reversible format rather than being displayed as hashed or masked values

You are affected if Junos Space version is 1.0 through 12.2 and the web UI is accessible with managed devices containing viewable or recoverable credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos Space to version 20.3R1 or later, which implements proper secure credential storage (non-reversible hashing). Additionally, mitigate XSS vulnerabilities and clear browser caches as a defense-in-depth measure.

Fix this in Junos Space Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-0220 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-0220 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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