| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in ServiceNow Now Platform. The impacted element is an unknown function. The manipulation results in incomplete blacklist. This vulnerability is known as CVE-2024-5217. It is possible to launch the attack remotely. Furthermore, an exploit is available. Applying a patch is advised to resolve this issue.
Details
A vulnerability classified as critical has been found in ServiceNow Now Platform (unknown version). Affected is an unknown code block. The manipulation with an unknown input leads to a incomplete blacklist vulnerability. CWE is classifying the issue as CWE-184. The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete, leading to resultant weaknesses. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
ServiceNow has addressed an input validation vulnerability that was identified in the Washington DC, Vancouver, and earlier Now Platform releases. This vulnerability could enable an unauthenticated user to remotely execute code within the context of the Now Platform. The vulnerability is addressed in the listed patches and hot fixes below, which were released during the June 2024 patching cycle. If you have not done so already, we recommend applying security patches relevant to your instance as soon as possible.
The weakness was published by Adam Kues as KB1648313. The advisory is shared for download at support.servicenow.com. This vulnerability is traded as CVE-2024-5217 since 05/22/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are unknown but an exploit is available. The MITRE ATT&CK project declares the attack technique as T1562.006.
It is declared as attacked. This issue was added on 07/29/2024 to the CISA Known Exploited Vulnerabilities Catalog with a due date of 08/19/2024:
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.Applying the patch 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 is able to eliminate this problem.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 9.0VulDB Meta Temp Score: 8.9
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 9.8
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Incomplete blacklistCWE: CWE-184 / CWE-183 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Attacked
EPSS Score: 🔍
EPSS Percentile: 🔍
KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 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
Timeline
05/22/2024 🔍07/10/2024 🔍
07/10/2024 🔍
03/19/2025 🔍
Sources
Advisory: KB1648313Researcher: Adam Kues
Status: Confirmed
CVE: CVE-2024-5217 (🔍)
GCVE (CVE): GCVE-0-2024-5217
GCVE (VulDB): GCVE-100-271080
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/10/2024 18:46Updated: 03/19/2025 20:06
Changes: 07/10/2024 18:46 (65), 07/10/2024 18:47 (1), 07/11/2024 09:18 (2), 07/12/2024 10:12 (2), 07/29/2024 19:25 (13), 07/30/2024 01:27 (11), 07/30/2024 18:29 (11), 09/09/2024 22:30 (1), 03/19/2025 20:06 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
I don't find this cpe inside the NIST NVD dictionary, rather I read the following
servicenow:servicenow
Could you please update?
Might our Artificial Intelligence support you?
Check our Alexa App!