Nosql Database vulnerabilitiesRanked by how likely they are to be used.

Product2 versions
The short answer

Nosql Database is made by Oracle. We track 12 published vulnerabilities in it, across 2 versions. None of them is on the list of flaws known to be exploited today. If you run Nosql Database, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Nosql Database vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Nosql Database's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Nosql Database flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 77%

    Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 'unknownProtocol' are established.

    CVSS7.5Published3 Mar 2021
  2. 51%

    Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform.

    CVSS7.5Published16 Feb 2021
  3. 37%

    Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to DNS rebinding attacks as the whitelist includes “localhost6”.

    CVSS7.5Published3 Mar 2021
  4. 13%

    FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the slf4j-ext class from polymorphic deserialization.

    CVSS9.8Published2 Jan 2019
  5. 9.2%

    The ZlibDecoders in Netty 4.1.x before 4.1.46 allow for unbounded memory allocation while decoding a ZlibEncoded byte stream.

    CVSS7.5Published7 Apr 2020
  6. 9.0%

    Apache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request...

    CVSS5.3Published2 Dec 2020
  7. 8.2%

    Apache Thrift Java client library versions 0.5.0 through 0.11.0 can bypass SASL negotiation isComplete validation in the org.apache.thrift.transport.TSaslTransport class.

    CVSS7.5Published7 Jan 2019
  8. 4.9%

    Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

    CVSS5.9Published30 Mar 2021
  9. 4.8%

    Fasterxml Jackson version Before 2.9.8 contains a CWE-20: Improper Input Validation vulnerability in Jackson-Modules-Java8 that can result in Causes a denial-of-service (DoS).

    CVSS6.5Published20 Dec 2018
  10. 2.2%

    A vulnerability was found in Hibernate-Validator.

    CVSS6.1Published8 Nov 2019
Precursor Intelligence

Running Nosql Database? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 12 published vulnerabilities listed under the name Nosql Database, across 2 versions.

None of Nosql Database's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Nosql Database. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.