Now Platform: Improper Neutralization of Special Elements used in an SQL Command
CVE-2024-8924 is a high-severity improper neutralization of special elements used in an SQL command vulnerability in Now Platform from ServiceNow, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions Utah Patch 10b Hot Fix 3, Vancouver Patch 8 Hot Fix 5, Vancouver Patch 9 Hot Fix 3b as the first without the flaw, so updating Now Platform to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Now Platform to Utah Patch 10b Hot Fix 3 or Vancouver Patch 8 Hot Fix 5 or Vancouver Patch 9 Hot Fix 3b or Vancouver Patch 10 Hot Fix 2, whichever matches your release line, or a later version.
- Update servicenow to Utah Patch 10b Hot Fix 3 or Vancouver Patch 8 Hot Fix 5 or Vancouver Patch 9 Hot Fix 3b or Vancouver Patch 10 Hot Fix 2, whichever matches your release line, or a later version.
- Read the advisory on support.servicenow.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| ServiceNow | Now Platform | before Utah Patch 10b Hot Fix 3; before Vancouver Patch 8 Hot Fix 5; before Vancouver Patch 9 Hot Fix 3b; before Vancouver Patch 10 Hot Fix 2; before Washington DC Patch 4 Hot Fix 2b; before Washington DC Patch 5 Hot Fix 6; before Washington DC Patch 6 Hot Fix 1; before Washington DC Patch 7; and 1 more ranges | Utah Patch 10b Hot Fix 3, Vancouver Patch 8 Hot Fix 5, Vancouver Patch 9 Hot Fix 3b, Vancouver Patch 10 Hot Fix 2, Washington DC Patch 4 Hot Fix 2b, Washington DC Patch 5 Hot Fix 6 |
| Servicenow | servicenow | Utah up to, but not including, Utah Patch 10b Hot Fix 3; Vancouver up to, but not including, Vancouver Patch 8 Hot Fix 5; Vancouver up to, but not including, Vancouver Patch 9 Hot Fix 3b; Vancouver up to, but not including, Vancouver Patch 10 Hot Fix 2; Washington_DC up to, but not including, Washington DC Patch 4 Hot Fix 2b; Washington_DC up to, but not including, Washington DC Patch 5 Hot Fix 6; Washington_DC up to, but not including, Washington DC Patch 6 Hot Fix 1; Washington_DC up to, but not including, Washington DC Patch 7; and 1 more ranges | Utah Patch 10b Hot Fix 3, Vancouver Patch 8 Hot Fix 5, Vancouver Patch 9 Hot Fix 3b, Vancouver Patch 10 Hot Fix 2, Washington DC Patch 4 Hot Fix 2b, Washington DC Patch 5 Hot Fix 6 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (servicenow.com) |
| CVSS 3.1 | 7.5 | High | CNA (servicenow.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
ServiceNow has addressed a blind SQL injection vulnerability that was identified in the Now Platform. This vulnerability could enable an unauthenticated user to extract unauthorized information. ServiceNow deployed an update to hosted instances, and ServiceNow provided the update to our partners and self-hosted customers. Further, the vulnerability is addressed in the listed patches and hot fixes.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in an SQL Command
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
How developers prevent this class of flaw
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
More Improper Neutralization of Special Elements used in an SQL Command vulnerabilities (CWE-89)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Now Platform
- 8.2 High severity
- 10.0 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
ServiceNow Improper Input Validation Exploited
Recent Improper Neutralization of Special Elements used in an SQL Command vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.