CVE-2023-41045: Graylog vulnerable to insecure source port usage for DNS queries

CVE-2023-41045 · Severity: low · CVSS 3.1 · Published 2023-07-06

Graylog vulnerable to insecure source port usage for DNS queries

Technologies: org.graylog2:graylog2-server (Maven). Vendors: Maven.

Quick answers

Is CVE-2023-41045 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-41045 being exploited in the wild.
How severe is CVE-2023-41045?
Low severity, with a CVSS score of 3.1, published 6 July 2023.
Which products and versions are affected?
org.graylog2:graylog2-server (Maven) ECOSYSTEM:introduced=5.1.0,fixed=5.1.3.
Is there a fix for CVE-2023-41045?
Yes. org.graylog2:graylog2-server (Maven): upgrade to 5.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-41045?
Check whether you run org.graylog2:graylog2-server (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.graylog2:graylog2-server (Maven): upgrade to 5.1.3 or later
    # set org.graylog2:graylog2-server to 5.1.3 in your pom.xml or build.gradle

Affected products

  • org.graylog2:graylog2-server (Maven) ECOSYSTEM:introduced=5.1.0,fixed=5.1.3

Identifiers

  • CVE-2023-41045
  • GHSA-g96c-x7rh-99r3

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