dbcve.org
Paragon Active Assurance Test AgentApplication · Juniper

CVE-2024-30406

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated

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
A Cleartext Storage in a File on Disk vulnerability in Juniper Networks Junos OS Evolved ACX Series devices using the Paragon Active Assurance Test Agent software installed on network devices allows a local, authenticated attacker with high privileges to read all other users login credentials. This issue affects only Juniper Networks Junos OS Evolved ACX Series devices using the Paragon Active Assurance Test Agent software installed on these devices from 23.1R1-EVO through 23.2R2-EVO.  This issue does not affect releases before 23.1R1-EVO.

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

Cleartext storage vulnerability in Paragon Active Assurance Test Agent on Junos OS Evolved ACX Series devices stores user login credentials in plaintext on disk. A local authenticated attacker with high privileges can read all other users' credentials from these unencrypted files.

MitigationUpdate Junos OS Evolved to a version beyond 23.2R2-EVO that includes the fix for this vulnerability. If immediate patching is not possible, review and restrict access to the Paragon Active Assurance Test Agent files and ensure only necessary personnel have high-privilege access.

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
Paragon Active Assurance Test AgentApplication
Affected:all versions
Junos Os EvolvedOperating system
Affected:= 23.1= 23.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
Local
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:H/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. Check Junos OS Evolved version
    Run 'show version' or 'version' command on the device to identify the installed Junos OS Evolved version
    Affected if The version is 23.1 or 23.2 (exactly matching these releases)
  2. Verify Paragon Active Assurance Test Agent presence
    Check if the Paragon Active Assurance Test Agent package or service is installed on the system by querying installed packages or running 'show system software'
    Affected if Paragon Active Assurance Test Agent is installed on the device
  3. Locate credential storage files
    Search for configuration or credential files related to Paragon Active Assurance Test Agent in the system directories, typically under the application's data path
    Affected if Plaintext credential files exist for Paragon Active Assurance Test Agent users
  4. Inspect credential file contents
    Read the contents of the Paragon Active Assurance Test Agent credential files using appropriate file inspection commands
    Affected if User credentials are stored in plaintext (unencrypted) within these files

A user is affected if they are running Junos OS Evolved version 23.1 or 23.2 with Paragon Active Assurance Test Agent installed, and plaintext credential files are present on the system.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Junos OS Evolved to a version beyond 23.2R2-EVO that includes the fix for this vulnerability. If immediate patching is not possible, review and restrict access to the Paragon Active Assurance Test Agent files and ensure only necessary personnel have high-privilege access.

Recommended fix Moderate confidence

Junos OS Evolved 23.3R1-EVO or later (23.4R1, 24.1, etc.)

  1. Identify the exact Junos OS Evolved version currently running on the ACX Series device using 'show version' command
  2. If running version 23.1R1-EVO through 23.2R2-EVO with Paragon Active Assurance Test Agent installed, plan an upgrade to a fixed release
  3. Upgrade to Junos OS Evolved release 23.3R1-EVO or later which contains the fix for CVE-2024-30406
  4. After upgrade, verify the fix by checking that credentials are no longer stored in cleartext on disk
  5. Alternatively, if upgrading is not immediately possible, contact Juniper Networks support for patch availability
Caveat Review Junos OS Evolved release notes for potential breaking changes between 23.2 and 23.3, particularly for ACX Series devices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Paragon Active Assurance Test Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30406 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-30406 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