LiveActive security incident?Get immediate response
CVE Record

CVE-2020-1624: Junos OS Evolved: objmon logs may leak sensitive information

A local, authenticated user with shell can obtain the hashed values of login passwords and shared secrets via raw objmon configuration files. 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-1624 can expose password hashes and shared secrets stored in raw objmon configuration files on Junos OS Evolved. An attacker needs a valid local shell account, so this is mainly an insider, compromised-admin, or post-compromise risk. The impact is confidentiality loss, not direct system takeover.

Executive priority

Treat this as a moderate-priority credential exposure issue. It is not remotely exploitable from the provided evidence, but it can increase blast radius if a local account is compromised. Prioritize internet-edge, shared-administration, and high-trust network devices.

Technical view

Junos OS Evolved versions before 19.1R1 may log or store sensitive configuration data in objmon raw configuration files. A local authenticated shell user can obtain hashed login passwords and shared secrets. The issue maps to CWE-532 and has CVSS 3.1 score 5.5: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.

Likely exposure

Exposure is limited to organizations running Junos OS Evolved before 19.1R1 where users have local shell access. Devices without local shell users, or already upgraded past the affected range, are less likely to be exposed based on the provided sources.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation requires local authenticated shell access. The main risk is that obtained hashes or shared secrets could support credential attacks or broader compromise if secrets are weak, reused, or not rotated.

Researcher notes

Evidence supports a local information disclosure condition affecting Junos OS Evolved before 19.1R1. The bundle does not provide exploit details, observed exploitation, or broader affected CPE data. Focus assessment on local shell exposure, sensitive file handling, and post-remediation secret rotation decisions.

Mitigation direction

  • Upgrade affected Junos OS Evolved systems to 19.1R1 or later, following Juniper guidance.
  • Restrict local shell access to administrators with a clear operational need.
  • Review vendor advisory JSA11003 for any environment-specific remediation instructions.
  • Rotate exposed or potentially exposed passwords and shared secrets if compromise is suspected.

Validation and detection

  • Inventory Junos OS Evolved devices and identify versions earlier than 19.1R1.
  • Review which accounts have local shell access on affected systems.
  • Check whether objmon raw configuration files are accessible to non-essential local users.
  • Confirm remediation by verifying the installed Junos OS Evolved release after maintenance.
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-532: 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-1624 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-1624Attack 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-532 · source CWE mapping

Insertion of Sensitive Information into Log File

Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.