First published: Wed Jul 10 2024(Updated: )
ServiceNow has addressed an input validation vulnerability that was identified in Vancouver and Washington DC Now Platform releases. This vulnerability could enable an unauthenticated user to remotely execute code within the context of the Now Platform. ServiceNow applied an update to hosted instances, and ServiceNow released the update to our partners and self-hosted customers. Listed below are the patches and hot fixes that address the vulnerability. If you have not done so already, we recommend applying security patches relevant to your instance as soon as possible.
Credit: psirt@servicenow.com psirt@servicenow.com
Affected Software | Affected Version | How to fix |
---|---|---|
ServiceNow | =utah | |
ServiceNow | =utah-early_availability | |
ServiceNow | =utah-patch_1 | |
ServiceNow | =utah-patch_1_hotfix_1 | |
ServiceNow | =utah-patch_1_hotfix_1a | |
ServiceNow | =utah-patch_1_hotfix_1b | |
ServiceNow | =utah-patch_1_hotfix_2 | |
ServiceNow | =utah-patch_10 | |
ServiceNow | =utah-patch_10_hotfix_1 | |
ServiceNow | =utah-patch_10_hotfix_2 | |
ServiceNow | =utah-patch_10a | |
ServiceNow | =utah-patch_10a_hotfix_1 | |
ServiceNow | =utah-patch_2 | |
ServiceNow | =utah-patch_2_hotfix_1 | |
ServiceNow | =utah-patch_2_hotfix_2 | |
ServiceNow | =utah-patch_2_hotfix_3 | |
ServiceNow | =utah-patch_2_hotfix_4 | |
ServiceNow | =utah-patch_3 | |
ServiceNow | =utah-patch_3_hotfix_1 | |
ServiceNow | =utah-patch_3_hotfix_1b | |
ServiceNow | =utah-patch_4 | |
ServiceNow | =utah-patch_4_hotfix_1 | |
ServiceNow | =utah-patch_4_hotfix_2 | |
ServiceNow | =utah-patch_4_hotfix_2a | |
ServiceNow | =utah-patch_4_hotfix_2b | |
ServiceNow | =utah-patch_4_hotfix_3 | |
ServiceNow | =utah-patch_4_hotfix_3b | |
ServiceNow | =utah-patch_4_hotfix_4 | |
ServiceNow | =utah-patch_4_hotfix_4b | |
ServiceNow | =utah-patch_4_hotfix_5 | |
ServiceNow | =utah-patch_5 | |
ServiceNow | =utah-patch_5_hotfix_1 | |
ServiceNow | =utah-patch_6 | |
ServiceNow | =utah-patch_6_hotfix_1 | |
ServiceNow | =utah-patch_6_hotfix_2 | |
ServiceNow | =utah-patch_7 | |
ServiceNow | =utah-patch_7_hotfix_1 | |
ServiceNow | =utah-patch_7_hotfix_2 | |
ServiceNow | =utah-patch_7a | |
ServiceNow | =utah-patch_7b | |
ServiceNow | =utah-patch_8 | |
ServiceNow | =utah-patch_8_hotfix_2 | |
ServiceNow | =utah-patch_9 | |
ServiceNow | =utah-patch_9_hotfix_1 | |
ServiceNow | =utah-patch_9_hotfix_1a | |
ServiceNow | =utah-patch_9_hotfix_1b | |
ServiceNow | =vancouver | |
ServiceNow | =vancouver-patch_1 | |
ServiceNow | =vancouver-patch_1_hotfix_1 | |
ServiceNow | =vancouver-patch_10 | |
ServiceNow | =vancouver-patch_2 | |
ServiceNow | =vancouver-patch_2_hotfix_1 | |
ServiceNow | =vancouver-patch_2_hotfix_1a | |
ServiceNow | =vancouver-patch_2_hotfix_2 | |
ServiceNow | =vancouver-patch_2_hotfix_3 | |
ServiceNow | =vancouver-patch_2_hotfix1a | |
ServiceNow | =vancouver-patch_3 | |
ServiceNow | =vancouver-patch_3_hotfix_1 | |
ServiceNow | =vancouver-patch_3_hotfix_2 | |
ServiceNow | =vancouver-patch_3_hotfix_3 | |
ServiceNow | =vancouver-patch_3_hotfix_4 | |
ServiceNow | =vancouver-patch_4 | |
ServiceNow | =vancouver-patch_4_hotfix_1 | |
ServiceNow | =vancouver-patch_4_hotfix_1a | |
ServiceNow | =vancouver-patch_4_hotfix_1b | |
ServiceNow | =vancouver-patch_4_hotfix_2b | |
ServiceNow | =vancouver-patch_5 | |
ServiceNow | =vancouver-patch_5_hotfix_1 | |
ServiceNow | =vancouver-patch_6 | |
ServiceNow | =vancouver-patch_6_hotfix_1 | |
ServiceNow | =vancouver-patch_7 | |
ServiceNow | =vancouver-patch_7_hotfix_1 | |
ServiceNow | =vancouver-patch_7_hotfix_1a | |
ServiceNow | =vancouver-patch_7_hotfix_2 | |
ServiceNow | =vancouver-patch_7_hotfix_2a | |
ServiceNow | =vancouver-patch_7_hotfix_2b | |
ServiceNow | =vancouver-patch_7_hotfix_3a | |
ServiceNow | =vancouver-patch_8 | |
ServiceNow | =vancouver-patch_8_hotfix_1 | |
ServiceNow | =vancouver-patch_8_hotfix_2 | |
ServiceNow | =vancouver-patch_8_hotfix_3 | |
ServiceNow | =vancouver-patch_9 | |
ServiceNow | =washington_dc | |
ServiceNow | =washington_dc-patch_1 | |
ServiceNow | =washington_dc-patch_1_hotfix_1 | |
ServiceNow | =washington_dc-patch_1_hotfix_2 | |
ServiceNow | =washington_dc-patch_1_hotfix_2a | |
ServiceNow | =washington_dc-patch_2 | |
ServiceNow | =washington_dc-patch_2_hotfix_1 | |
ServiceNow | =washington_dc-patch_3 | |
ServiceNow Now Platform |
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-4879 is classified as a critical vulnerability that allows remote code execution.
To fix CVE-2024-4879, users should apply the latest security patch provided by ServiceNow for the affected versions.
CVE-2024-4879 affects ServiceNow releases Utah, Vancouver, and Washington DC.
Yes, CVE-2024-4879 can be exploited remotely by unauthenticated users, allowing them to execute code.
CVE-2024-4879 could enable harmful actions within the Now Platform, potentially leading to data breaches.