Use of a Broken or Risky Cryptographic Algorithm in PostgreSQL

Severity: low · CVSS 3.1 · Published 2022-02-15

Use of a Broken or Risky Cryptographic Algorithm in PostgreSQL

Technologies: org.postgresql:postgresql (Maven). Vendors: Maven.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Low severity, with a CVSS score of 3.1, published 15 February 2022.
Which products and versions are affected?
org.postgresql:postgresql (Maven) ECOSYSTEM:introduced=0,fixed=13.1.
Is there a fix for This vulnerability?
Yes. org.postgresql:postgresql (Maven): upgrade to 13.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected?
Check whether you run org.postgresql:postgresql (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.postgresql:postgresql (Maven): upgrade to 13.1 or later
    # set org.postgresql:postgresql to 13.1 in your pom.xml or build.gradle

Affected products

  • org.postgresql:postgresql (Maven) ECOSYSTEM:introduced=0,fixed=13.1

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.