Overview 207 matches · 39 in Waratek scope · 6 protected · 3 exploited · 0 CISA KEV · 5 public PoC · 1 EPSS ≥ 0.5
207matches
39in Waratek scope18.8%
6protected2.9%
3exploited1.4%
0CISA KEV0.0%
5public PoC2.4%
1EPSS ≥ 0.50.5%
Protected by Waratek
6
2.9%
Rule in development
0
0.0%
Mitigation candidate
1
0.5%
No exploit published
32
15.5%
Outside Waratek scope
3
1.4%
Not applicable
164
79.2%
Withdrawn CVE
1
0.5%
blocked by ARMR today
6
2.9%
partly blocked
0
0.0%
not blocked
201
97.1%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 40 / year
20102
Not applicable2
Medium2
not blocked2
No public exploit2
20110
20120
20131
Not applicable1
High1
not blocked1
No public exploit1
20142
Not applicable2
Medium2
not blocked2
No public exploit2
20151
Not applicable1
Medium1
not blocked1
No public exploit1
20161
Not applicable1
High1
not blocked1
No public exploit1
20174
Not applicable4
High2
Medium2
not blocked4
No public exploit4
201815
No exploit published2
Outside Waratek scope1
Not applicable12
Critical4
High10
Medium1
not blocked15
Exploited1
Proof of concept only1
No public exploit13
20199
Protected by Waratek1
Not applicable8
Critical3
High5
Medium1
blocked by ARMR today1
not blocked8
No public exploit9
202018
Protected by Waratek2
No exploit published1
Not applicable15
Critical7
High10
Medium1
blocked by ARMR today2
not blocked16
No public exploit18
202140
Protected by Waratek2
No exploit published2
Not applicable35
Withdrawn CVE1
Critical11
High12
Medium16
Unknown1
blocked by ARMR today2
not blocked38
Working exploit published1
No public exploit39
202228
Mitigation candidate1
No exploit published3
Not applicable24
Critical11
High10
Medium7
not blocked28
Proof of concept only11
No public exploit17
202339
No exploit published18
Outside Waratek scope1
Not applicable20
Critical9
High24
Medium6
not blocked39
Proof of concept only21
No public exploit18
202413
No exploit published1
Not applicable12
Critical4
High6
Medium3
not blocked13
Proof of concept only7
No public exploit6
202513
No exploit published1
Not applicable12
Critical2
High5
Medium5
Low1
not blocked13
Proof of concept only7
No public exploit6
202621
Protected by Waratek1
No exploit published4
Outside Waratek scope1
Not applicable15
Critical3
High11
Medium7
blocked by ARMR today1
not blocked20
Exploited2
Proof of concept only9
No public exploit10
201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-41714 | Medium | 2022-11-03 | Not applicable | Proof of concept only | fastest-json-copy version 1.0.1 allows an external attacker to edit or add new properties to an object. This is possible because the application does not correctly validate the incoming JSON keys, thus allowing the '__proto__' property to be edited. |
| CVE-2022-42227 | High | 2022-10-19 | Not applicable | Proof of concept only | jsonlint 1.0 is vulnerable to heap-buffer-overflow via /home/hjsz/jsonlint/src/lexer. |
| CVE-2022-41382 | Critical | 2022-10-11 | Not applicable | No public exploit | The d8s-json package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. The backdoor is the democritus-file-system package. The affected version is 0.1.0. |
| CVE-2022-38882 | Critical | 2022-09-19 | Not applicable | No public exploit | The d8s-json for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. The backdoor is the democritus-strings package. The affected version is 0.1.0. |
| CVE-2022-25921 | Critical | 2022-08-29 | Not applicable | No public exploit | All versions of package morgan-json are vulnerable to Arbitrary Code Execution due to missing sanitization of input passed to the Function constructor. |
| CVE-2022-23460 | High | 2022-08-19 | Not applicable | No public exploit | Jsonxx or Json++ is a JSON parser, writer and reader written in C++. In affected versions of jsonxx json parsing may lead to stack exhaustion in an address sanitized (ASAN) build. This issue may lead to Denial of Service if the program using the jsonxx library crashes. This issue exists on the current commit of the jsonxx project and the project itself has been archived. Updates are not expected. Users are advised to find a replacement. |
| CVE-2022-23459 | Critical | 2022-08-19 | Not applicable | No public exploit | Jsonxx or Json++ is a JSON parser, writer and reader written in C++. In affected versions of jsonxx use of the Value class may lead to memory corruption via a double free or via a use after free. The value class has a default assignment operator which may be used with pointer types which may point to alterable data where the pointer itself is not updated. This issue exists on the current commit of the jsonxx project. The project itself has been archived and updates are not expected. Users are advised to find a replacement. |
| CVE-2022-36010 | Critical | 2022-08-15 | Not applicable | Proof of concept only | This library allows strings to be parsed as functions and stored as a specialized component, [`JsonFunctionValue`](https://github.com/oxyno-zeta/react-editable-json-tree/blob/09a0ca97835b0834ad054563e2fddc6f22bc5d8c/src/components/JsonFunctionValue.js). To do this, Javascript's [`eval`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval) function is used to execute strings that begin with "function" as Javascript. This unfortunately could allow arbitrary code to be executed if it exists as a value within the JSON structure being displayed. Given that this component may often be used to display data from arbitrary, untrusted sources, this is extremely dangerous. One important note is that users who have defined a custom [`onSubmitValueParser`](https://github.com/oxyno-zeta/react-editable-json-tree/tree/09a0ca97835b0834ad054563e2fddc6f22bc5d8c#onsubmitvalueparser) callback prop on the [`JsonTree`](https://github.com/oxyno-zeta/react-editable-json-tree/blob/09a0ca97835b0834ad054563e2fddc6f22bc5d8c/src/JsonTree.js) component should be ***unaffected***. This vulnerability exists in the default `onSubmitValueParser` prop which calls [`parse`](https://github.com/oxyno-zeta/react-editable-json-tree/blob/master/src/utils/parse.js#L30). Prop is added to `JsonTree` called `allowFunctionEvaluation`. This prop will be set to `true` in v2.2.2, which allows upgrade without losing backwards-compatibility. In v2.2.2, we switched from using `eval` to using [`Function`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function) to construct anonymous functions. This is better than `eval` for the following reasons: - Arbitrary code should not be able to execute immediately, since the `Function` constructor explicitly *only creates* anonymous functions - Functions are created without local closures, so they only have access to the global scope If you use: - **Version `<2.2.2`**, you must upgrade as soon as possible. - **Version `^2.2.2`**, you must explicitly set `JsonTree`'s `allowFunctionEvaluation` prop to `false` to fully mitigate this vulnerability. - **Version `>=3.0.0`**, `allowFunctionEvaluation` is already set to `false` by default, so no further steps are necessary. |
| CVE-2022-31117 | Medium | 2022-07-05 | Not applicable | No public exploit | UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. In versions prior to 5.4.0 an error occurring while reallocating a buffer for string decoding can cause the buffer to get freed twice. Due to how UltraJSON uses the internal decoder, this double free is impossible to trigger from Python. This issue has been resolved in version 5.4.0 and all users should upgrade to UltraJSON 5.4.0. There are no known workarounds for this issue. |
| CVE-2022-31116 | High | 2022-07-05 | Not applicable | Proof of concept only | UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Affected versions were found to improperly decode certain characters. JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries. All users parsing JSON from untrusted sources are vulnerable. From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library's `json` module does, preserving them in the parsed output. Users are advised to upgrade. There are no known workarounds for this issue. |
| CVE-2022-25845 | Critical | 2022-06-10 | Mitigation candidate | Proof of concept only | The package com.alibaba:fastjson before 1.2.83 are vulnerable to Deserialization of Untrusted Data by bypassing the default autoType shutdown restrictions, which is possible under certain conditions. Exploiting this vulnerability allows attacking remote servers. Workaround: If upgrading is not possible, you can enable [safeMode](https://github.com/alibaba/fastjson/wiki/fastjson_safemode). |
| CVE-2022-30241 | Medium | 2022-05-04 | Not applicable | No public exploit | The jquery.json-viewer library through 1.4.0 for Node.js does not properly escape characters such as < in a JSON object, as demonstrated by a SCRIPT element. |
| CVE-2022-23631 | Critical | 2022-02-09 | Not applicable | No public exploit | superjson is a program to allow JavaScript expressions to be serialized to a superset of JSON. In versions prior to 1.8.1 superjson allows input to run arbitrary code on any server using superjson input without prior authentication or knowledge. The only requirement is that the server implements at least one endpoint which uses superjson during request processing. This has been patched in superjson 1.8.1. Users are advised to update. There are no known workarounds for this issue. |
| CVE-2021-45958 | Medium | 2022-01-01 | Not applicable | No public exploit | UltraJSON (aka ujson) through 5.1.0 has a stack-based buffer overflow in Buffer_AppendIndentUnchecked (called from encode). Exploitation can, for example, use a large amount of indentation. |
| CVE-2021-3918 | Critical | 2021-11-13 | Not applicable | No public exploit | json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') |
| CVE-2020-23879 | High | 2021-11-10 | Not applicable | No public exploit | pdf2json v0.71 was discovered to contain a NULL pointer dereference in the component ObjectStream::getObject. |
| CVE-2020-23878 | Critical | 2021-11-10 | Not applicable | No public exploit | pdf2json v0.71 was discovered to contain a stack buffer overflow in the component XRef::fetch. |
| CVE-2021-23820 | Critical | 2021-11-03 | Not applicable | No public exploit | This affects all versions of package json-pointer. A type confusion vulnerability can lead to a bypass of CVE-2020-7709 when the pointer components are arrays. |
| CVE-2021-23807 | Critical | 2021-11-03 | Not applicable | No public exploit | This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays. |
| CVE-2021-23509 | Critical | 2021-11-03 | Not applicable | No public exploit | This affects the package json-ptr before 3.0.0. A type confusion vulnerability can lead to a bypass of CVE-2020-7766 when the user-provided keys used in the pointer parameter are arrays. |
| CVE-2021-42836 | High | 2021-10-22 | Not applicable | No public exploit | GJSON before 1.9.3 allows a ReDoS (regular expression denial of service) attack. |
| CVE-2021-3822 | High | 2021-09-27 | Not applicable | No public exploit | jsoneditor is vulnerable to Inefficient Regular Expression Complexity |
| CVE-2021-23441 | Unknown | 2021-09-19 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none |
| CVE-2020-19475 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function CCITTFaxStream::lookChar in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to an invalid write of size 2 . |
| CVE-2020-19474 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function Gfx::doShowText in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to an Use After Free . |
| CVE-2020-19473 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function DCTStream::decodeImage in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to an uncaught floating point exception. |
| CVE-2020-19472 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function DCTStream::readHuffSym in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to an invalid read of size 2 . |
| CVE-2020-19471 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function DCTStream::decodeImage in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to an invalid read of size 4 . |
| CVE-2020-19470 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function DCTStream::getChar in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to a NULL pointer dereference (invalid read of size 1) . |
| CVE-2020-19469 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function DCTStream::reset in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to an invalid write of size 8 . |
| CVE-2020-19468 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function EmbedStream::getChar in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to a null pointer derefenrece (invalid read of size 8) . |
| CVE-2020-19467 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function DCTStream::transformDataUnit in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to an Illegal Use After Free . |
| CVE-2020-19466 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function DCTStream::transformDataUnit in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to an invalid read of size 1 . |
| CVE-2020-19465 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function ObjectStream::getObject in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to an invalid read of size 4 . |
| CVE-2020-19464 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function XRef::fetch in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to a stack overflow . |
| CVE-2020-19463 | Medium | 2021-07-21 | Not applicable | No public exploit | An issue has been found in function vfprintf in PDF2JSON 0.70 that allows attackers to cause a Denial of Service due to a stack overflow. |
| CVE-2021-31684 | High | 2021-06-01 | No exploit published | No public exploit | A vulnerability was discovered in the indexOf function of JSONParserByteArray in JSON Smart versions 1.3 and 2.4 which causes a denial of service (DOS) via a crafted web request. |
| CVE-2018-1107 | Medium | 2021-03-30 | Not applicable | No public exploit | It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU time when validated. |
| CVE-2021-27568 | Medium | 2021-02-23 | Protected by Waratek | No public exploit | An issue was discovered in netplex json-smart-v1 through 2015-10-23 and json-smart-v2 through 2.4. An exception is thrown from a function, but it is not caught, as demonstrated by NumberFormatException. When it is not caught, it may cause programs using the library to crash or expose sensitive information. |
| CVE-2020-28429 | Critical | 2021-02-23 | Not applicable | Working exploit published | All versions of package geojson2kml are vulnerable to Command Injection via the index.js file. PoC: var a =require("geojson2kml"); a("./","& touch JHU",function(){}) |
| CVE-2020-18750 | High | 2021-02-05 | Not applicable | No public exploit | Buffer overflow in pdf2json 0.69 allows local users to execute arbitrary code by converting a crafted PDF file. |
| CVE-2021-23900 | High | 2021-01-13 | No exploit published | No public exploit | OWASP json-sanitizer before 1.2.2 can output invalid JSON or throw an undeclared exception for crafted input. This may lead to denial of service if the application is not prepared to handle these situations. |
| CVE-2021-23899 | Critical | 2021-01-13 | Protected by Waratek | No public exploit | OWASP json-sanitizer before 1.2.2 may emit closing SCRIPT tags and CDATA section delimiters for crafted input. This allows an attacker to inject arbitrary HTML or XML into embedding documents. |
| CVE-2020-23849 | Medium | 2021-01-11 | Not applicable | No public exploit | Stored XSS was discovered in the tree mode of jsoneditor before 9.0.2 through injecting and executing JavaScript. |
| CVE-2020-36067 | High | 2021-01-05 | Not applicable | No public exploit | GJSON <=v1.6.5 allows attackers to cause a denial of service (panic: runtime error: slice bounds out of range) via a crafted GET call. |
| CVE-2020-36066 | High | 2021-01-05 | Not applicable | No public exploit | GJSON <1.6.5 allows attackers to cause a denial of service (remote) via crafted JSON. |
| CVE-2016-20008 | High | 2021-01-01 | Not applicable | No public exploit | The REST/JSON project 7.x-1.x for Drupal allows session enumeration, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy. |
| CVE-2016-20007 | High | 2021-01-01 | Not applicable | No public exploit | The REST/JSON project 7.x-1.x for Drupal allows session name guessing, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy. |
| CVE-2016-20006 | High | 2021-01-01 | Not applicable | No public exploit | The REST/JSON project 7.x-1.x for Drupal allows blockage of user logins, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy. |
| CVE-2016-20005 | Critical | 2021-01-01 | Not applicable | No public exploit | The REST/JSON project 7.x-1.x for Drupal allows user registration bypass, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy. |
| CVE-2016-20004 | Critical | 2021-01-01 | Not applicable | No public exploit | The REST/JSON project 7.x-1.x for Drupal allows field access bypass, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy. |
| CVE-2016-20003 | High | 2021-01-01 | Not applicable | No public exploit | The REST/JSON project 7.x-1.x for Drupal allows user enumeration, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy. |
| CVE-2016-20002 | Critical | 2021-01-01 | Not applicable | No public exploit | The REST/JSON project 7.x-1.x for Drupal allows comment access bypass, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy. |
| CVE-2016-20001 | Critical | 2021-01-01 | Not applicable | No public exploit | The REST/JSON project 7.x-1.x for Drupal allows node access bypass, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy. |
| CVE-2020-29203 | Critical | 2020-12-26 | Not applicable | No public exploit | struct2json before 2020-11-18 is affected by a Buffer Overflow because strcpy is used for S2J_STRUCT_GET_string_ELEMENT. |
| CVE-2020-22083 | Critical | 2020-12-17 | Not applicable | No public exploit | jsonpickle through 1.4.1 allows remote code execution during deserialization of a malicious payload through the decode() function. Note: It has been argued that this is expected and clearly documented behaviour. pickle is known to be capable of causing arbitrary code execution, and must not be used with un-trusted data |
| CVE-2020-35381 | High | 2020-12-15 | Not applicable | No public exploit | jsonparser 1.0.0 allows attackers to cause a denial of service (panic: runtime error: slice bounds out of range) via a GET call. |
| CVE-2020-35380 | High | 2020-12-15 | Not applicable | No public exploit | GJSON before 1.6.4 allows attackers to cause a denial of service via crafted JSON. |
| CVE-2020-7770 | Critical | 2020-11-12 | Not applicable | No public exploit | This affects the package json8 before 1.0.3. The function adds in the target object the property specified in the path, however it does not properly check the key being set, leading to a prototype pollution. |
| CVE-2020-7766 | Critical | 2020-11-10 | Not applicable | No public exploit | This affects all versions of package json-ptr. The issue occurs in the set operation (https://flitbit.github.io/json-ptr/classes/_src_pointer_.jsonpointer.htmlset) when the force flag is set to true. The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution. |
| CVE-2020-8268 | High | 2020-11-09 | Not applicable | No public exploit | Prototype pollution vulnerability in json8-merge-patch npm package < 1.0.3 may allow attackers to inject or modify methods and properties of the global object constructor. |
| CVE-2020-7709 | High | 2020-10-05 | Not applicable | No public exploit | This affects the package json-pointer before 0.6.1. Multiple reference of object using slash is supported. |
| CVE-2020-8237 | High | 2020-09-18 | Not applicable | No public exploit | Prototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack. |
| CVE-2020-7712 | High | 2020-08-30 | Protected by Waratek | No public exploit | This affects the package json before 10.0.0. It is possible to inject arbritary commands using the parseLookup function. |
| CVE-2020-17479 | Critical | 2020-08-10 | Not applicable | No public exploit | jpv (aka Json Pattern Validator) before 2.2.2 does not properly validate input, as demonstrated by a corrupted array. |
| CVE-2020-13973 | Medium | 2020-06-09 | No exploit published | No public exploit | OWASP json-sanitizer before 1.2.1 allows XSS. An attacker who controls a substring of the input JSON, and controls another substring adjacent to a SCRIPT element in which the output is embedded as JavaScript, may be able to confuse the HTML parser as to where the SCRIPT element ends, and cause non-script content to be interpreted as JavaScript. |
| CVE-2018-21234 | Critical | 2020-05-21 | Protected by Waratek | No public exploit | Jodd before 5.0.4 performs Deserialization of Untrusted JSON Data when setClassMetadataName is set. |
| CVE-2020-12762 | High | 2020-05-09 | Not applicable | No public exploit | json-c through 0.14 has an integer overflow and out-of-bounds write via a large JSON file, as demonstrated by printbuf_memappend. |
| CVE-2020-10663 | High | 2020-04-28 | Not applicable | No public exploit | The JSON gem through 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, 2.5 through 2.5.7, and 2.6 through 2.6.5, has an Unsafe Object Creation Vulnerability. This is quite similar to CVE-2013-0269, but does not rely on poor garbage-collection behavior within Ruby. Specifically, use of JSON parsing methods can lead to creation of a malicious object within the interpreter, with adverse effects that are application-dependent. |
| CVE-2020-10675 | High | 2020-03-19 | Not applicable | No public exploit | The Library API in buger jsonparser through 2019-12-04 allows attackers to cause a denial of service (infinite loop) via a Delete call. |
| CVE-2020-10594 | Critical | 2020-03-15 | Not applicable | No public exploit | An issue was discovered in drf-jwt 1.15.x before 1.15.1. It allows attackers with access to a notionally invalidated token to obtain a new, working token via the refresh endpoint, because the blacklist protection mechanism is incompatible with the token-refresh feature. NOTE: drf-jwt is a fork of jpadilla/django-rest-framework-jwt, which is unmaintained. |
| CVE-2019-3683 | High | 2020-01-17 | Not applicable | No public exploit | The keystone-json-assignment package in SUSE Openstack Cloud 8 before commit d7888c75505465490250c00cc0ef4bb1af662f9f every user listed in the /etc/keystone/user-project-map.json was assigned full "member" role access to every project. This allowed these users to access, modify, create and delete arbitrary resources, contrary to expectations. |
| CVE-2019-19507 | Medium | 2019-12-02 | Not applicable | No public exploit | In jpv (aka Json Pattern Validator) before 2.1.1, compareCommon() can be bypassed because certain internal attributes can be overwritten via a conflicting name, as demonstrated by 'constructor': {'name':'Array'}. This affects validate(). Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result. |
| CVE-2019-18848 | High | 2019-11-12 | Not applicable | No public exploit | The json-jwt gem before 1.11.0 for Ruby lacks an element count during the splitting of a JWE string. |
| CVE-2019-15550 | High | 2019-08-26 | Not applicable | No public exploit | An issue was discovered in the simd-json crate before 0.1.15 for Rust. There is an out-of-bounds read and an incorrect crossing of a page boundary. |
| CVE-2019-1010239 | High | 2019-07-19 | Not applicable | No public exploit | DaveGamble/cJSON cJSON 1.7.8 is affected by: Improper Check for Unusual or Exceptional Conditions. The impact is: Null dereference, so attack can cause denial of service. The component is: cJSON_GetObjectItemCaseSensitive() function. The attack vector is: crafted json file. The fixed version is: 1.7.9 and later. |
| CVE-2019-0188 | High | 2019-05-28 | Protected by Waratek | No public exploit | Apache Camel prior to 2.24.0 contains an XML external entity injection (XXE) vulnerability (CWE-611) due to using an outdated vulnerable JSON-lib library. This affects only the camel-xmljson component, which was removed. |
| CVE-2019-11835 | Critical | 2019-05-09 | Not applicable | No public exploit | cJSON before 1.7.11 allows out-of-bounds access, related to multiline comments. |
| CVE-2019-11834 | Critical | 2019-05-09 | Not applicable | No public exploit | cJSON before 1.7.11 allows out-of-bounds access, related to \x00 in a string literal. |
| CVE-2016-10749 | Critical | 2019-04-29 | Not applicable | No public exploit | parse_string in cJSON.c in cJSON before 2016-10-02 has a buffer over-read, as demonstrated by a string that begins with a " character and ends with a \ character. |
| CVE-2018-17937 | High | 2019-03-13 | Not applicable | No public exploit | gpsd versions 2.90 to 3.17 and microjson versions 1.0 to 1.3, an open source project, allow a stack-based buffer overflow, which may allow remote attackers to execute arbitrary code on embedded platforms via traffic on Port 2947/TCP or crafted JSON inputs. |
| CVE-2018-18854 | High | 2018-10-31 | No exploit published | No public exploit | Lightbend Spray spray-json through 1.3.4 allows remote attackers to cause a denial of service (resource consumption) because of Algorithmic Complexity during the parsing of many JSON object fields (with keys that have the same hash code). |
| CVE-2018-18853 | High | 2018-10-31 | No exploit published | No public exploit | Lightbend Spray spray-json through 1.3.4 allows remote attackers to cause a denial of service (resource consumption) because of Algorithmic Complexity during the parsing of a field composed of many decimal digits. |
| CVE-2017-18349 | Critical | 2018-10-23 | Outside Waratek scope | Exploited | parseObject in Fastjson before 1.2.25, as used in FastjsonEngine in Pippo 1.11.0 and other products, allows remote attackers to execute arbitrary code via a crafted JSON request, as demonstrated by a crafted rmi:// URI in the dataSourceName field of HTTP POST data to the Pippo /json URI, which is mishandled in AjaxApplication.java. |
| CVE-2018-17072 | Critical | 2018-09-16 | Not applicable | No public exploit | JSON++ through 2016-06-15 has a buffer over-read in yyparse() in json.y. |
| CVE-2018-14632 | High | 2018-09-06 | Not applicable | No public exploit | An out of bound write can occur when patching an Openshift object using the 'oc patch' functionality in OpenShift Container Platform before 3.7. An attacker can use this flaw to cause a denial of service attack on the Openshift master api service which provides cluster management. |
| CVE-2018-1000217 | Critical | 2018-08-20 | Not applicable | No public exploit | Dave Gamble cJSON version 1.7.3 and earlier contains a CWE-416: Use After Free vulnerability in cJSON library that can result in Possible crash, corruption of data or even RCE. This attack appear to be exploitable via Depends on how application uses cJSON library. If application provides network interface then can be exploited over a network, otherwise just local.. This vulnerability appears to have been fixed in 1.7.4. |
| CVE-2018-1000216 | High | 2018-08-20 | Not applicable | No public exploit | Dave Gamble cJSON version 1.7.2 and earlier contains a CWE-415: Double Free vulnerability in cJSON library that can result in Possible crash or RCE. This attack appear to be exploitable via Attacker must be able to force victim to print JSON data, depending on how cJSON library is used this could be either local or over a network. This vulnerability appears to have been fixed in 1.7.3. |
| CVE-2018-1000215 | High | 2018-08-20 | Not applicable | No public exploit | Dave Gamble cJSON version 1.7.6 and earlier contains a CWE-772 vulnerability in cJSON library that can result in Denial of Service (DoS). This attack appear to be exploitable via If the attacker can force the data to be printed and the system is in low memory it can force a leak of memory. This vulnerability appears to have been fixed in 1.7.7. |
| CVE-2018-14947 | High | 2018-08-05 | Not applicable | No public exploit | An issue has been found in PDF2JSON 0.69. XmlFontAccu::CSStyle in XmlFonts.cc has Mismatched Memory Management Routines (operator new [] versus operator delete). |
| CVE-2018-14946 | High | 2018-08-05 | Not applicable | No public exploit | An issue has been found in PDF2JSON 0.69. The HtmlString class in ImgOutputDev.cc has Mismatched Memory Management Routines (malloc versus operator delete). |
| CVE-2018-1000539 | Medium | 2018-06-26 | Not applicable | No public exploit | Nov json-jwt version >= 0.5.0 && < 1.9.4 contains a CWE-347: Improper Verification of Cryptographic Signature vulnerability in Decryption of AES-GCM encrypted JSON Web Tokens that can result in Attacker can forge a authentication tag. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 1.9.4 and later. |
| CVE-2017-16113 | High | 2018-06-07 | Not applicable | No public exploit | The parsejson module is vulnerable to regular expression denial of service when untrusted user input is passed into it to be parsed. |
| CVE-2016-10610 | High | 2018-06-01 | Not applicable | No public exploit | unicode-json is a unicode lookup table. unicode-json before 2.0.0 downloads data resources over HTTP, which leaves it vulnerable to MITM attacks. |
| CVE-2015-9235 | Critical | 2018-05-29 | Not applicable | Proof of concept only | In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family). |
| CVE-2018-1000096 | High | 2018-03-13 | Not applicable | No public exploit | brianleroux tiny-json-http version all versions since commit 9b8e74a232bba4701844e07bcba794173b0238a8 (Oct 29 2016) contains a Missing SSL certificate validation vulnerability in The libraries core functionality is affected. that can result in Exposes the user to man-in-the-middle attacks. |
| CVE-2014-4616 | Medium | 2017-08-24 | Not applicable | No public exploit | Array index error in the scanstring function in the _json module in Python 2.7 through 3.5 and simplejson before 2.6.1 allows context-dependent attackers to read arbitrary process memory via a negative index value in the idx argument to the raw_decode function. |
| CVE-2017-0256 | Medium | 2017-05-12 | Not applicable | No public exploit | A spoofing vulnerability exists when the ASP.NET Core fails to properly sanitize web requests. |
| CVE-2017-0249 | High | 2017-05-12 | Not applicable | No public exploit | An elevation of privilege vulnerability exists when the ASP.NET Core fails to properly sanitize web requests. |
| CVE-2017-0247 | High | 2017-05-12 | Not applicable | No public exploit | A denial of service vulnerability exists when the ASP.NET Core fails to properly validate web requests. NOTE: Microsoft has not commented on third-party claims that the issue is that the TextEncoder.EncodeCore function in the System.Text.Encodings.Web package in ASP.NET Core Mvc before 1.0.4 and 1.1.x before 1.1.3 allows remote attackers to cause a denial of service by leveraging failure to properly calculate the length of 4-byte characters in the Unicode Non-Character range. |