Back to vendor advisories
Microsoft Security Response CenterCVE-2025-22868

Unexpected memory consumption during token parsing in golang.org/x/oauth2

HighVendor CVSS 7.5 / 10 1 CVE Published Mar 8, 2025 at 12:00 AM UTC

Summary

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?

One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information.

If impact to additional products is identified, we will update the CVE to reflect this.

Products covered

  • azl3 azcopy 10.25.1-4 on Azure Linux 3.0

  • azl3 cert-manager 1.12.15-3 on Azure Linux 3.0

  • azl3 prometheus 2.45.4-12 on Azure Linux 3.0

  • azl3 influxdb 2.7.5-5 on Azure Linux 3.0

  • azl3 packer 1.9.5-9 on Azure Linux 3.0

  • azl3 containerized-data-importer 1.57.0-14 on Azure Linux 3.0

  • cbl2 vitess 17.0.7-8 on CBL Mariner 2.0

  • cbl2 azcopy 10.25.1-5 on CBL Mariner 2.0

Show 45 more products
  • cbl2 blobfuse2 2.1.2-8 on CBL Mariner 2.0

  • cbl2 coredns 1.11.1-18 on CBL Mariner 2.0

  • cbl2 kubernetes 1.28.4-18 on CBL Mariner 2.0

  • cbl2 cert-manager 1.11.2-22 on CBL-Mariner 2.0

  • cbl2 node-problem-detector 0.8.17-6 on CBL-Mariner 2.0

  • cbl2 packer 1.9.5-13 on CBL-Mariner 2.0

  • cbl2 azcopy 10.25.1-5 on CBL-Mariner 2.0

  • cbl2 coredns 1.11.1-18 on CBL-Mariner 2.0

  • cbl2 kubernetes 1.28.4-18 on CBL-Mariner 2.0

  • cbl2 telegraf 1.29.4-16 on CBL-Mariner 2.0

  • cbl2 telegraf 1.29.4-11 on CBL Mariner 2.0

  • cbl2 kubernetes 1.28.4-15 on CBL Mariner 2.0

  • cbl2 coredns 1.11.1-14 on CBL Mariner 2.0

  • cbl2 moby-engine 24.0.9-15 on CBL Mariner 2.0

  • cbl2 azcopy 10.25.1-3 on CBL Mariner 2.0

  • cbl2 vitess 17.0.7-5 on CBL Mariner 2.0

  • cbl2 packer 1.9.5-10 on CBL Mariner 2.0

  • cbl2 cert-manager 1.11.2-20 on CBL Mariner 2.0

  • azl3 telegraf 1.31.0-5 on Azure Linux 3.0

  • azl3 coredns 1.11.4-3 on Azure Linux 3.0

  • azl3 moby-engine 25.0.3-11 on Azure Linux 3.0

  • azl3 containerized-data-importer 1.57.0-13 on Azure Linux 3.0

  • azl3 keda 2.14.1-3 on Azure Linux 3.0

  • azl3 packer 1.9.5-6 on Azure Linux 3.0

  • azl3 influxdb 2.7.5-2 on Azure Linux 3.0

  • azl3 prometheus 2.45.4-8 on Azure Linux 3.0

  • azl3 vitess 19.0.4-5 on Azure Linux 3.0

  • azl3 node-problem-detector 0.8.20-2 on Azure Linux 3.0

  • azl3 cert-manager 1.12.15-2 on Azure Linux 3.0

  • azl3 azcopy 10.25.1-2 on Azure Linux 3.0

  • azl3 kubernetes 1.30.10-2 on Azure Linux 3.0

  • azl3 kubernetes 1.30.10-7 on Azure Linux 3.0

  • azl3 vitess 19.0.4-7 on Azure Linux 3.0

  • azl3 keda 2.14.1-7 on Azure Linux 3.0

  • azl3 moby-engine 25.0.3-13 on Azure Linux 3.0

  • azl3 coredns 1.11.4-6 on Azure Linux 3.0

  • azl3 telegraf 1.31.0-10 on Azure Linux 3.0

  • cbl2 cert-manager 1.11.2-22 on CBL Mariner 2.0

  • cbl2 node-problem-detector 0.8.17-6 on CBL Mariner 2.0

  • cbl2 packer 1.9.5-13 on CBL Mariner 2.0

  • cbl2 moby-engine 24.0.9-17 on CBL Mariner 2.0

  • cbl2 telegraf 1.29.4-16 on CBL Mariner 2.0

  • cbl2 vitess 17.0.7-8 on CBL-Mariner 2.0

  • cbl2 moby-engine 24.0.9-17 on CBL-Mariner 2.0

  • cbl2 blobfuse2 2.1.2-8 on CBL-Mariner 2.0

Remediation

CBL-Mariner Releases

Vendor-listed fixes

  • 10.25.1-2

  • 1.12.15-2

  • 2.45.4-8

  • 2.7.5-2

  • 1.9.5-6

  • 1.57.0-13

  • 17.0.7-5

  • 10.25.1-3

Show 15 more fixes
  • 2.1.2-8

  • 1.11.1-14

  • 1.28.4-15

  • 1.11.2-20

  • 0.8.17-6

  • 1.9.5-10

  • 1.29.4-11

  • 24.0.9-15

  • 1.31.0-5

  • 1.11.4-3

  • 25.0.3-11

  • 2.14.1-3

  • 19.0.4-5

  • 0.8.20-2

  • 1.30.10-2

CVEs in this advisory 1

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  3. Added to SecurityAlert

    We collected the advisory from the official source.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.