ServiceNow
Utah, Vancouver, and Washington DC Now Platform
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2024-5217 | 10 Jul 2024 | Now Platform: < Utah Patch 10 Hot Fix 3, < Utah Patch 10a Hot Fix 2, < Utah Patch 10b Hot Fix 1, < Vancouver Patch 6 Hot Fix 2, < Vancouver Patch 7 Hot Fix 3b, < Vancouver Patch 8 Hot Fix 4, < Vancouver Patch 9 Hot Fix 1, < Vancouver Patch 10, < Washington DC Patch 1 Hot Fix 3b, < Washington DC Patch 2 Hot Fix 2, < Washington DC Patch 3 Hot Fix 2, < Washington DC Patch 4, < Washington DC Patch 5 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-4879 | 10 Jul 2024 | Now Platform: < Utah Patch 10 Hot Fix 3, < Utah Patch 10a Hot Fix 2, < Vancouver Patch 6 Hot Fix 2, < Vancouver Patch 7 Hot Fix 3b, < Vancouver Patch 8 Hot Fix 4, < Vancouver Patch 9, < Vancouver Patch 10, < Washington DC Patch 1 Hot Fix 2b, < Washington DC Patch 2 Hot Fix 2, < Washington DC Patch 3 Hot Fix 1, < Washington DC Patch 4 | 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.