CVE-2021-33198: High severity IBM Security Guardium Insights vulnerability

Published Mar 10, 2021
·
Updated

A flaw was found in Go, where it attempts to allocate excessive memory. This issue may cause panic or unrecoverable fatal error if passed inputs with very large exponents. The highest threat from this vulnerability is to system availability.

Other sources

Go before 1.15.12 and 1.16.x before 1.16.5 attempts to allocate excessive memory (issue 2 of 2).

References: https://github.com/golang/go/issues/44910 https://groups.google.com/g/golang-announce/c/RgCMkAEQjSI

— Red Hat

Golang Go is vulnerable to a denial of service, caused by a flaw in the SetString and UnmarshalText methods of math/big.Rat. By sending a specially-crafted input, a remote attacker could exploit this vulnerability to cause a panic or an unrecoverable fatal error, and results in a denial of service condition.

— IBM

In Go before 1.15.13 and 1.16.x before 1.16.5 there can be a panic for a large exponent to the math/big.Rat SetString or UnmarshalText method.

— Microsoft

In Go before 1.15.13 and 1.16.x before 1.16.5, there can be a panic for a large exponent to the math/big.Rat SetString or UnmarshalText method.

Affected Software

43 affected componentsFixes available
redhat/openshift-serverless-clients<0:0.23.2-1.el8
0:0.23.2-1.el8
redhat/skopeo<2:1.9.2-1.el9
2:1.9.2-1.el9
redhat/buildah<1:1.27.0-2.el9
1:1.27.0-2.el9
redhat/ignition<0:2.6.0-8.rhaos4.6.git947598e.el8
0:2.6.0-8.rhaos4.6.git947598e.el8
redhat/atomic-openshift-service-idler<0:4.7.0-202107291238.p0.git.39cfc66.assembly.stream.el8
0:4.7.0-202107291238.p0.git.39cfc66.assembly.stream.el8
redhat/cri-o<0:1.20.4-7.rhaos4.7.git6287500.el7
0:1.20.4-7.rhaos4.7.git6287500.el7
redhat/ignition<0:2.9.0-4.rhaos4.7.git1d56dc8.el8
0:2.9.0-4.rhaos4.7.git1d56dc8.el8
redhat/openshift<0:4.7.0-202107292242.p0.git.558d959.assembly.stream.el7
0:4.7.0-202107292242.p0.git.558d959.assembly.stream.el7
redhat/openshift-clients<0:4.7.0-202107292242.p0.git.8b4b094.assembly.stream.el8
0:4.7.0-202107292242.p0.git.8b4b094.assembly.stream.el8
redhat/redhat-release-coreos<0:47.84-1.el8
0:47.84-1.el8
redhat/cri-o<0:1.21.2-8.rhaos4.8.git8d4264e.el7
0:1.21.2-8.rhaos4.8.git8d4264e.el7
redhat/ignition<0:2.9.0-7.rhaos4.8.el8
0:2.9.0-7.rhaos4.8.el8
redhat/openshift<0:4.8.0-202107300027.p0.git.38b3ecc.assembly.stream.el7
0:4.8.0-202107300027.p0.git.38b3ecc.assembly.stream.el7
redhat/openshift-clients<0:4.8.0-202107292313.p0.git.1077b05.assembly.stream.el7
0:4.8.0-202107292313.p0.git.1077b05.assembly.stream.el7
redhat/containernetworking-plugins<0:0.8.6-3.rhaos4.6.el7
0:0.8.6-3.rhaos4.6.el7
redhat/cri-tools<0:1.21.0-3.el8
0:1.21.0-3.el8
redhat/golang-github-prometheus-promu<0:0.5.0-4.git642a960.el8
0:0.5.0-4.git642a960.el8
redhat/butane<0:0.12.1-2.rhaos4.8.el8
0:0.12.1-2.rhaos4.8.el8
redhat/mcg<0:5.9.0-28.61dcf87.5.9.el8
0:5.9.0-28.61dcf87.5.9.el8
redhat/etcd<0:3.3.23-3.1.el8
0:3.3.23-3.1.el8
redhat/kubevirt<0:2.6.10-230.el7
0:2.6.10-230.el7
redhat/kubevirt<0:4.8.5-278.el7
0:4.8.5-278.el7
redhat/kubevirt<0:2.6.10-230.el8
0:2.6.10-230.el8
redhat/kubevirt<0:4.8.5-278.el8
0:4.8.5-278.el8
IBM Security Guardium Insights<=3.0
Golang Go<1.15.13
Golang Go>=1.16.0<1.16.5
Microsoft azl3 python-tensorboard 2.11.0-3
Microsoft azl3 python-tensorboard 2.16.2-2
redhat/go<1.16.5
1.16.5
redhat/go<1.15.13
1.15.13
alpine/go>=1.16.0<1.15.13-r0
1.15.13-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0
alpine/go>=1.16.0<1.16.5-r0
1.16.5-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/openshift-serverless-clients to a version that resolves this vulnerability.

    Fixed in 0:0.23.2-1.el8
  2. Upgrade

    Upgrade redhat/skopeo to a version that resolves this vulnerability.

    Fixed in 2:1.9.2-1.el9
  3. Upgrade

    Upgrade redhat/buildah to a version that resolves this vulnerability.

    Fixed in 1:1.27.0-2.el9
  4. Upgrade

    Upgrade redhat/ignition to a version that resolves this vulnerability.

    Fixed in 0:2.6.0-8.rhaos4.6.git947598e.el8
  5. Upgrade

    Upgrade redhat/atomic-openshift-service-idler to a version that resolves this vulnerability.

    Fixed in 0:4.7.0-202107291238.p0.git.39cfc66.assembly.stream.el8
  6. Upgrade

    Upgrade redhat/cri-o to a version that resolves this vulnerability.

    Fixed in 0:1.20.4-7.rhaos4.7.git6287500.el7
  7. Upgrade

    Upgrade redhat/ignition to a version that resolves this vulnerability.

    Fixed in 0:2.9.0-4.rhaos4.7.git1d56dc8.el8
  8. Upgrade

    Upgrade redhat/openshift to a version that resolves this vulnerability.

    Fixed in 0:4.7.0-202107292242.p0.git.558d959.assembly.stream.el7
  9. Upgrade

    Upgrade redhat/openshift-clients to a version that resolves this vulnerability.

    Fixed in 0:4.7.0-202107292242.p0.git.8b4b094.assembly.stream.el8
  10. Upgrade

    Upgrade redhat/redhat-release-coreos to a version that resolves this vulnerability.

    Fixed in 0:47.84-1.el8
  11. Upgrade

    Upgrade redhat/cri-o to a version that resolves this vulnerability.

    Fixed in 0:1.21.2-8.rhaos4.8.git8d4264e.el7
  12. Upgrade

    Upgrade redhat/ignition to a version that resolves this vulnerability.

    Fixed in 0:2.9.0-7.rhaos4.8.el8
  13. Upgrade

    Upgrade redhat/openshift to a version that resolves this vulnerability.

    Fixed in 0:4.8.0-202107300027.p0.git.38b3ecc.assembly.stream.el7
  14. Upgrade

    Upgrade redhat/openshift-clients to a version that resolves this vulnerability.

    Fixed in 0:4.8.0-202107292313.p0.git.1077b05.assembly.stream.el7
  15. Upgrade

    Upgrade redhat/containernetworking-plugins to a version that resolves this vulnerability.

    Fixed in 0:0.8.6-3.rhaos4.6.el7
  16. Upgrade

    Upgrade redhat/cri-tools to a version that resolves this vulnerability.

    Fixed in 0:1.21.0-3.el8
  17. Upgrade

    Upgrade redhat/golang-github-prometheus-promu to a version that resolves this vulnerability.

    Fixed in 0:0.5.0-4.git642a960.el8
  18. Upgrade

    Upgrade redhat/butane to a version that resolves this vulnerability.

    Fixed in 0:0.12.1-2.rhaos4.8.el8
  19. Upgrade

    Upgrade redhat/mcg to a version that resolves this vulnerability.

    Fixed in 0:5.9.0-28.61dcf87.5.9.el8
  20. Upgrade

    Upgrade redhat/etcd to a version that resolves this vulnerability.

    Fixed in 0:3.3.23-3.1.el8
  21. Upgrade

    Upgrade redhat/kubevirt to a version that resolves this vulnerability.

    Fixed in 0:2.6.10-230.el7
  22. Upgrade

    Upgrade redhat/kubevirt to a version that resolves this vulnerability.

    Fixed in 0:4.8.5-278.el7
  23. Upgrade

    Upgrade redhat/kubevirt to a version that resolves this vulnerability.

    Fixed in 0:2.6.10-230.el8
  24. Upgrade

    Upgrade redhat/kubevirt to a version that resolves this vulnerability.

    Fixed in 0:4.8.5-278.el8
  25. Upgrade

    Upgrade redhat/go to a version that resolves this vulnerability.

    Fixed in 1.16.5
  26. Upgrade

    Upgrade redhat/go to a version that resolves this vulnerability.

    Fixed in 1.15.13
  27. Upgrade

    Upgrade alpine/go to a version that resolves this vulnerability.

    Fixed in 1.15.13-r0
  28. Upgrade

    Upgrade alpine/go to a version that resolves this vulnerability.

    Fixed in 1.16.5-r0

Event History

Mar 10, 2021
CVE Published
12:00 AM
Aug 2, 2021
CVE Published
via MITRE·06:55 PM
Data Sourced
via MITRE·06:55 PM
Description
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via OSV·07:15 PM
DescriptionSeverityAffected Software
Aug 3, 2021
Data Sourced
via Red Hat·01:35 PM
DescriptionSeverityAffected Software
Sep 11, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the vulnerability ID for this flaw in Golang Go?

The vulnerability ID is CVE-2021-33198.

2

What is the severity rating of CVE-2021-33198?

CVE-2021-33198 has a severity rating of high.

3

How does this vulnerability in Golang Go cause a denial of service?

The vulnerability in Golang Go can cause a panic or unrecoverable fatal error, resulting in a denial of service.

4

Is there a patch available for IBM Security Guardium Insights?

Yes, a patch is available for IBM Security Guardium Insights. You can find it at the provided URL.

5

How do I fix CVE-2021-33198 in Go?

To fix CVE-2021-33198 in Go, you need to update to version 1.16.5 or 1.15.13, depending on the version you are using.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203