CVE Vulnerabilities

CVE-2024-21589

Improper Access Control

Published: Jan 12, 2024 | Modified: Nov 21, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

An Improper Access Control vulnerability in the Juniper Networks Paragon Active Assurance Control Center allows an unauthenticated network-based attacker to access reports without authenticating, potentially containing sensitive configuration information.

A feature was introduced in version 3.1.0 of the Paragon Active Assurance Control Center which allows users to selectively share account data. By exploiting this vulnerability, it is possible to access reports without being logged in, resulting in the opportunity for malicious exfiltration of user data.

Note that the Paragon Active Assurance Control Center SaaS offering is not affected by this issue.

This issue affects Juniper Networks Paragon Active Assurance versions 3.1.0, 3.2.0, 3.2.2, 3.3.0, 3.3.1, 3.4.0.

This issue does not affect Juniper Networks Paragon Active Assurance versions earlier than 3.1.0.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Paragon_active_assurance_control_center Juniper 3.1.0 (including) 3.1.0 (including)
Paragon_active_assurance_control_center Juniper 3.2.0 (including) 3.2.0 (including)
Paragon_active_assurance_control_center Juniper 3.2.2 (including) 3.2.2 (including)
Paragon_active_assurance_control_center Juniper 3.3.0 (including) 3.3.0 (including)
Paragon_active_assurance_control_center Juniper 3.3.1 (including) 3.3.1 (including)
Paragon_active_assurance_control_center Juniper 3.4.0 (including) 3.4.0 (including)

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References