| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in is-my-json-valid up to 2.12.3. The affected element is an unknown function of the component Regex Handler. Executing a manipulation can lead to input validation. This vulnerability is handled as CVE-2016-2537. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability has been found in is-my-json-valid up to 2.12.3 and classified as critical. This vulnerability affects some unknown functionality of the component Regex Handler. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect availability. CVE summarizes:
The is-my-json-valid package before 2.12.4 for Node.js has an incorrect exports['utc-millisec'] regular expression, which allows remote attackers to cause a denial of service (blocked event loop) via a crafted string.
The weakness was released 02/23/2016 (Website). The advisory is shared for download at nodesecurity.io. This vulnerability was named CVE-2016-2537 since 02/21/2016. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.12.4 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2017-0222). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD 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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: is-my-json-valid 2.12.4
Patch: github.com
Timeline
02/21/2016 🔍02/23/2016 🔍
02/23/2016 🔍
02/24/2016 🔍
10/18/2025 🔍
Sources
Advisory: eca4beb21e61877d76fdf6bea771f72f39544d9bStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2016-2537 (🔍)
GCVE (CVE): GCVE-0-2016-2537
GCVE (VulDB): GCVE-100-81076
EUVD: 🔍
Entry
Created: 02/24/2016 09:29Updated: 10/18/2025 04:34
Changes: 02/24/2016 09:29 (49), 08/09/2018 07:37 (8), 07/08/2022 13:43 (5), 10/18/2025 04:34 (17)
Complete: 🔍
Cache ID: 216:4A9:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.