CVE-2021-0205

When the Intrusion Detection Service (IDS) feature is configured on Juniper Networks MX series with a dynamic firewall filter using IPv6 source or destination prefix, it may incorrectly match the prefix as /32, causing the filter to block unexpected traffic. This issue affects only IPv6 prefixes when used as source and destination. This issue affects MX Series devices using MS-MPC, MS-MIC or MS-SPC3 service cards with IDS service configured. This issue affects: Juniper Networks Junos OS 17.3 versions prior to 17.3R3-S10 on MX Series; 17.4 versions prior to 17.4R3-S3 on MX Series; 18.1 versions prior to 18.1R3-S11 on MX Series; 18.2 versions prior to 18.2R3-S6 on MX Series; 18.3 versions prior to 18.3R3-S4 on MX Series; 18.4 versions prior to 18.4R3-S6 on MX Series; 19.1 versions prior to 19.1R2-S2, 19.1R3-S3 on MX Series; 19.2 versions prior to 19.2R3-S1 on MX Series; 19.3 versions prior to 19.3R2-S5, 19.3R3-S1 on MX Series; 19.4 versions prior to 19.4R3 on MX Series; 20.1 versions prior to 20.1R2 on MX Series; 20.2 versions prior to 20.2R2 on MX Series;

Weakness

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

Affected Software

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.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/19.html
• https://cwe.mitre.org/data/definitions/441.html
• https://cwe.mitre.org/data/definitions/478.html
• https://cwe.mitre.org/data/definitions/479.html
• https://cwe.mitre.org/data/definitions/502.html
• https://cwe.mitre.org/data/definitions/503.html
• https://cwe.mitre.org/data/definitions/536.html
• https://cwe.mitre.org/data/definitions/546.html
• https://cwe.mitre.org/data/definitions/550.html
• https://cwe.mitre.org/data/definitions/551.html
• https://cwe.mitre.org/data/definitions/552.html
• https://cwe.mitre.org/data/definitions/556.html
• https://cwe.mitre.org/data/definitions/558.html
• https://cwe.mitre.org/data/definitions/562.html
• https://cwe.mitre.org/data/definitions/563.html
• https://cwe.mitre.org/data/definitions/564.html
• https://cwe.mitre.org/data/definitions/578.html

References

• https://kb.juniper.net/JSA11095
• https://kb.juniper.net/JSA11095