Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY672 SECURITY RECORDS

Juniper Networks, Inc.

Junos OS

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2024-39565 10 Jul 2024 < 21.2R3-S8; 21.4 < 21.4R3-S7; 22.2 < 22.2R3-S4; 22.3 < 22.3R3-S3; 22.4 < 22.4R3-S2; 23.2 < 23.2R2; 23.4 < 23.4R1-S1, 23.4R2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-39561 10 Jul 2024 < 21.2R3-S8; 21.4 < 21.4R3-S7; 22.1 < 22.1R3-S6; 22.2 < 22.2R3-S4; 22.3 < 22.3R3-S3; 22.4 < 22.4R3-S2; 23.2 < 23.2R2; 23.4 < 23.4R1-S1, 23.4R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-39560 10 Jul 2024 < 20.4R3-S9; 21.2R1 < 21.2*; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S5; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S2; 22.4 < 22.4R3; 23.2 < 23.2R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-39558 10 Jul 2024 < 20.4R3-S10; 21.2 < 21.2R3-S7; 21.4 < 21.4R3-S6; 22.1 < 22.1R3-S5; 22.2 < 22.2R3-S3; 22.3 < 22.3R3; 22.4 < 22.4R2; < 20.4R3-S10-EVO No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-39556 10 Jul 2024 < 21.4R3-S7; 22.1 < 22.1R3-S6; 22.2 < 22.2R3-S4; 22.3 < 22.3R3-S3; 22.4 < 22.4R3-S2; 23.2 < 23.2R2; 23.4 < 23.4R1-S1, 23.4R2; < 21.4R3-S7-EVO No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-39555 10 Jul 2024 < 21.4R3-S8; 22.2 < 22.2R3-S4; 22.3 < 22.3R3-S3; 22.4 < 22.4R3-S3; 23.2 < 23.2R2-S1; 23.4 < 23.4R1-S2, 23.4R2; < 21.4R3-S8-EVO; 22.2-EVO < 22.2R3-S4-EVO No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-39554 10 Jul 2024 21.1 < 21.1*; 21.2 < 21.2R3-S7; 21.4 < 21.4R3-S6; 22.1 < 22.1R3-S5; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S2; 22.4 < 22.4R3; 23.2 < 23.2R2 < 21.1R1; < 21.1R1-EVO Update reference ↗
CVE-2024-21586 1 Jul 2024 21.4 < 21.4R3-S7.9; 22.1 < 22.1R3-S5.3; 22.2 < 22.2R3-S4.11; 22.3 < 22.3R3; 22.4 < 22.4R3; 21.4 < 21.4R3-S8; 22.1; 22.2 < 22.2R3-S5 < 21.4R1 Update reference ↗
CVE-2024-30380 16 Apr 2024 < 20.4R3-S9; 21.2 < 21.2R3-S7; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S4; 22.1 < 22.1R3-S4; 22.2 < 22.2R3-S2; 22.3 < 22.3R2-S2, 22.3R3-S1; 22.4 < 22.4R2-S2, 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30378 16 Apr 2024 < 20.4R3-S5; 21.1 < 21.1R3-S4; 21.2 < 21.2R3-S3; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S5; 22.1 < 22.1R3; 22.2 < 22.2R3; 22.3 < 22.3R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30402 12 Apr 2024 20.4 < 20.4R3-S10; 21.2 < 21.2R3-S7; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S4; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S1; 22.4 < 22.4R3; 23.2 < 23.2R1-S2, 23.2R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30401 12 Apr 2024 21.2 < 21.2R3-S1; 21.4 < 21.4R3; 22.1 < 22.1R2; 22.2 < 22.2R2 < 20.3R1; 20.4 Update reference ↗
CVE-2024-30398 12 Apr 2024 21.2 < 21.2R3-S7; 21.4 < 21.4R3-S6; 22.1 < 22.1R3-S5; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S2; 22.4 < 22.4R3; 23.2 < 23.2R1-S2, 23.2R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30397 12 Apr 2024 < 20.4R3-S10; 21.2 < 21.2R3-S7; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S4; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S1; 22.4 < 22.4R3; 23.2 < 23.2R1-S2, 23.2R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30391 12 Apr 2024 < 20.4R3-S7; 21.1 < 21.1R3; 21.2 < 21.2R2-S1, 21.2R3; 21.3 < 21.3R1-S2, 21.3R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30389 12 Apr 2024 21.4 < 21.4R3-S6 21.4 < 21.4R1 Update reference ↗
CVE-2024-30386 12 Apr 2024 < 20.4R3-S8; 21.2 < 21.2R3-S6; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S4; 22.1 < 22.1R3-S3; 22.2 < 22.2R3-S1; 22.3 < 22.3R3; 22.4 < 22.4R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30384 12 Apr 2024 < 20.4R3-S10; 21.2 < 21.2R3-S7; 21.4 < 21.4R3-S6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30382 12 Apr 2024 < 20.4R3-S10; 21.2 < 21.2R3-S8; 21.3 < 21.3R3; 21.4 < 21.4R3; 22.1 < 22.1R2; < 21.2R3-S8-EVO; 21.3 < 21.3R3-EVO; 21.4 < 21.4R3-EVO No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30387 12 Apr 2024 < 20.4R3-S9; 21.2 < 21.2R3-S5; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S4; 22.1 < 22.1R3-S2; 22.2 < 22.2R3-S2; 22.3 < 22.3R2-S2, 22.3R3; 22.4 < 22.4R2, 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30388 12 Apr 2024 20.4R3-S4 < 20.4R3-S8; 21.2R3-S2 < 21.2R3-S6; 21.4R2 < 21.4R3-S4; 22.1R2 < 22.1R3-S3; 22.2 < 22.2R3-S1; 22.3 < 22.3R2-S2, 22.3R3; 22.4 < 22.4R2-S1, 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30392 12 Apr 2024 < 21.2R3-S6; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S3; 22.2 < 22.2R3-S1; 22.3 < 22.3R2-S2, 22.3R3; 22.4 < 22.4R2-S1, 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30394 12 Apr 2024 < 21.2R3-S7; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S4; 22.2 < 22.2R3-S2; 22.3 < 22.3R3-S1; 22.4 < 22.4R3; 23.2 < 23.2R2; < 21.4R3-S5-EVO No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30395 12 Apr 2024 < 21.2R3-S7; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S5; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S2; 22.4 < 22.4R3; 23.2 < 23.2R1-S2, 23.2R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30405 12 Apr 2024 < 21.2R3-S7; 21.4 < 21.4R3-S6; 22.1 < 22.1R3-S5; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S2; 22.4 < 22.4R3; 23.2 < 23.2R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30409 12 Apr 2024 22.1 < 22.1R1-S2, 22.1R2; 22.1-EVO < 22.1R1-S2-EVO, 22.1R2-EVO No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21618 12 Apr 2024 21.4 < 21.4R3-S4; 22.1 < 22.1R3-S4; 22.2 < 22.2R3-S2; 22.3 < 22.3R2-S2, 22.3R3-S1; 22.4 < 22.4R3; 23.2 < 23.2R2; 21.4-EVO < 21.4R3-S5-EVO; 22.1-EVO < 22.1R3-S4-EVO < 21.4R1; < 21.4R1-EVO Update reference ↗
CVE-2024-21615 12 Apr 2024 < 21.2R3-S7; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S5; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S2; 22.4 < 22.4R3; 23.2 < 23.2R1-S2; < 21.2R3-S7-EVO No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21610 12 Apr 2024 < 20.4R3-S9; 21.2 < 21.2R3-S7; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S4; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S2; 22.4 < 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21609 12 Apr 2024 < 20.4R3-S9; 21.2 < 21.2R3-S7; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S4; 22.1 < 22.1R3-S3; 22.2 < 22.2R3-S2; 22.3 < 22.3R3; 22.4 < 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21605 12 Apr 2024 21.2R3-S3 < 21.2R3-S6; 22.1R3 < 22.1R3-S4; 22.2R2 < 22.2R3-S2; 22.3R2 < 22.3R3-S1; 22.4 < 22.4R2-S2, 22.4R3; 23.2 < 23.2R1-S1, 23.2R2 21.4 < 21.4* Update reference ↗
CVE-2024-21598 12 Apr 2024 20.4 < 20.4R3-S9; 21.2 < 21.2R3-S7; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S4; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S1; 22.4 < 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21593 12 Apr 2024 21.4R3 < 21.4R3-S5; 22.2R2 < 22.2R3-S2; 22.3R1 < 22.3R2-S2; 22.3R3 < 22.3R3-S1; 22.4R1 < 22.4R2-S2, 22.4R3; 23.2 < 23.2R1-S1, 23.2R2 22.1 Update reference ↗
CVE-2024-21620 25 Jan 2024 < 20.4R3-S10; 21.2 < 21.2R3-S8; 21.4 < 21.4R3-S6; 22.1 < 22.1R3-S5; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S2; 22.4 < 22.4R3-S1; 23.2 < 23.2R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21619 25 Jan 2024 < 20.4R3-S9; 21.2 < 21.2R3-S7; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S6; 22.1 < 22.1R3-S5; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S2; 22.4 < 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21617 12 Jan 2024 21.2 < 21.2R3-S5; 21.3 < 21.3R3-S4; 21.4 < 21.4R3-S4; 22.1 < 22.1R3-S2; 22.2 < 22.2R3-S2; 22.3 < 22.3R2-S1, 22.3R3; 22.4 < 22.4R1-S2, 22.4R2 < 20.4R3-S7 Update reference ↗
CVE-2024-21616 12 Jan 2024 < 21.2R3-S6; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S4; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S1; 22.4 < 22.4R2-S2, 22.4R3; 23.2 < 23.2R1-S1, 23.2R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21614 12 Jan 2024 22.2 < 22.2R2-S2, 22.2R3; 22.3 < 22.3R2, 22.3R3; 22.2 < 22.2R2-S2-EVO, 22.2R3-EVO; 22.3 < 22.3R2-EVO, 22.3R3-EVO No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21613 12 Jan 2024 < 21.2R3-S3; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S3; 22.1 < 22.1R3; 22.2 < 22.2R3; < 21.3R3-S5-EVO; 21.4 < 21.4R3-EVO; 22.1 < 22.1R3-EVO No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21611 12 Jan 2024 21.4 < 21.4R3; 22.1 < 22.1R3; 22.2 < 22.2R3; 21.4-EVO < 21.4R3-EVO; 22.1-EVO < 22.1R3-EVO; 22.2-EVO < 22.2R3-EVO No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21607 12 Jan 2024 < 20.4R3-S7; 21.1 < 21.1R3-S5; 21.2 < 21.2R3-S5; 21.3 < 21.3R3-S4; 21.4 < 21.4R3-S4; 22.1 < 22.1R3-S2; 22.2 < 22.2R3-S2; 22.3 < 22.3R2-S2, 22.3R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21606 12 Jan 2024 < 20.4R3-S8; 21.2 < 21.2R3-S6; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S3; 22.2 < 22.2R3-S3; 22.3 < 22.3R3-S1; 22.4 < 22.4R2-S2, 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21603 12 Jan 2024 < 20.4R3-S9; 21.2 < 21.2R3-S6; 21.3 < 21.3R3-S5; 21.4 < 21.4R3; 22.1 < 22.1R3; 22.2 < 22.2R2; 22.3 < 22.3R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21601 12 Jan 2024 21.2 < 21.2R3-S5; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S4; 22.1 < 22.1R3-S3; 22.2 < 22.2R3-S1; 22.3 < 22.3R2-S2, 22.3R3; 22.4 < 22.4R2-S1, 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21600 12 Jan 2024 < 20.4R3-S8; 21.1 < 21.1R3-S4; 21.2 < 21.2R3-S6; 21.3 < 21.3R3-S3; 21.4 < 21.4R3-S5; 22.1 < 22.1R2-S2, 22.1R3; 22.2 < 22.2R2-S1, 22.2R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21599 12 Jan 2024 < 20.4R3-S3; 21.1 < 21.1R3-S4; 21.2 < 21.2R3; 21.3 < 21.3R2-S1, 21.3R3; 21.4 < 21.4R2; 22.1 < 22.1R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21597 12 Jan 2024 < 20.4R3-S9; 21.2 < 21.2R3-S3; 21.4 < 21.4R3-S5; 22.1 < 22.1R3; 22.2 < 22.2R3; 22.3 < 22.3R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21596 12 Jan 2024 < 20.4R3-S9; 21.2 < 21.2R3-S7; 21.3 < 21.3R3-S5; 21.4 < 21.4R3-S5; 22.1 < 22.1R3-S4; 22.2 < 22.2R3-S2; 22.3 < 22.3R3-S1; 22.4 < 22.4R2-S2, 22.4R3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21595 12 Jan 2024 21.4R3 < 21.4R3-S4; 22.1R3 < 22.1R3-S3; 22.2R2 < 22.2R3-S1; 22.3 < 22.3R2-S2, 22.3R3; 22.4 < 22.4R2; 23.1 < 23.1R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-21594 12 Jan 2024 < 20.4R3-S6; 21.1 < 21.1R3-S5; 21.2 < 21.2R3-S4; 21.3 < 21.3R3-S3; 21.4 < 21.4R3-S3; 22.1 < 22.1R3-S1; 22.2 < 22.2R3; 22.3 < 22.3R2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.