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

Juniper Networks

NorthStar Controller Application

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-2017-2322 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2334 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2333 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2332 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2331 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2330 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2329 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2328 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2327 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2326 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2325 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2324 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2323 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2321 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2320 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2319 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2318 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2317 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-2316 24 Apr 2017 prior to version 2.1.0 Service Pack 1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗

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.