LiveActive security incident?Get immediate response
CVE Record

CVE-2020-1622: Junos OS Evolved: EvoSharedObjStore may leak sensitive information

A local, authenticated user with shell can obtain the hashed values of login passwords and shared secrets via the EvoSharedObjStore. This issue affects all versions of Junos OS Evolved prior to 19.1R1.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-1622 is a confidentiality issue in Juniper Junos OS Evolved before 19.1R1. A logged-in local user with shell access could obtain hashed login passwords and shared secrets from EvoSharedObjStore. This is not a remote internet-facing bug, but it increases insider and post-compromise risk.

Executive priority

Treat this as a moderate-priority network infrastructure issue. It is not described as remotely exploitable, but leaked password hashes and shared secrets can worsen a breach. Prioritize affected devices with broad shell access or sensitive network roles.

Technical view

The CVE describes exposure of sensitive stored values through EvoSharedObjStore to a local authenticated shell user. CVSS 3.1 is 5.5, with local attack vector, low complexity, low privileges required, no user interaction, unchanged scope, and high confidentiality impact only.

Likely exposure

Exposure is limited to organizations running Juniper Networks Junos OS Evolved versions prior to 19.1R1, where users or processes have shell access. Standard Junos OS is not named in the provided affected product list.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Abuse would require local authenticated shell access, so practical risk is highest after credential compromise, excessive administrator access, or misuse by a trusted user.

Researcher notes

Evidence is limited to the CVE metadata and Juniper reference in the bundle. Do not claim remote exploitation or active exploitation from these sources. Key validation is version-based exposure plus review of local shell access paths and secret-rotation needs.

Mitigation direction

  • Upgrade Junos OS Evolved systems running versions prior to 19.1R1.
  • Confirm the correct fixed release and guidance in Juniper advisory JSA11003.
  • Restrict shell access to only users with a clear operational need.
  • Review and remove stale local accounts and unnecessary administrative access.
  • Rotate affected passwords or shared secrets where exposure is plausible.

Validation and detection

  • Inventory Junos OS Evolved devices and record exact release versions.
  • Identify any systems running releases earlier than 19.1R1.
  • Review who has shell access on affected devices.
  • Check whether privileged or shared secrets require rotation after remediation.
  • Document remediation status against Juniper advisory JSA11003.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-664: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-1622 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2020-1622Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OS EvolvedunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-664 · source CWE mapping

Improper Control of a Resource Through its Lifetime

Improper Control of a Resource Through its Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.