CVE-2021-29923: Input Validation

Published Mar 22, 2021
·
Updated

A flaw was found in golang. Extraneous zero characters at the beginning of an IP address octet are not properly considered which could allow an attacker to bypass IP-based access controls. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Other sources

Go before 1.17 does not properly consider extraneous zero characters at the beginning of an IP address octet which (in some situations) allows attackers to bypass access control that is based on IP addresses because of unexpected octal interpretation. This affects net.ParseIP and net.ParseCIDR.

— Microsoft

Go before 1.17 does not properly consider extraneous zero characters at the beginning of an IP address octet, which (in some situations) allows attackers to bypass access control that is based on IP addresses, because of unexpected octal interpretation. This affects net.ParseIP and net.ParseCIDR.

Golang Go could allow a remote attacker to bypass security restrictions, caused by improper consideration for extraneous zero characters at the beginning of an IP address octet. By sending a specially-crafted request, an attacker could exploit this vulnerability to bypass access control based on IP addresses.

— IBM

Affected Software

26 affected componentsFixes available
redhat/openshift-serverless-clients<0:0.26.0-2.el8
0:0.26.0-2.el8
redhat/kiali<0:v1.24.7.redhat1-1.el8
0:v1.24.7.redhat1-1.el8
redhat/servicemesh<0:2.0.9-3.el8
0:2.0.9-3.el8
redhat/servicemesh-prometheus<0:2.14.0-16.el8.1
0:2.14.0-16.el8.1
redhat/servicemesh-proxy<0:2.0.9-3.el8
0:2.0.9-3.el8
redhat/go-toolset<1.15-golang-0:1.15.14-2.el7_9
1.15-golang-0:1.15.14-2.el7_9
redhat/butane<0:0.13.1-2.rhaos4.9.el8
0:0.13.1-2.rhaos4.9.el8
redhat/cri-o<0:1.22.1-17.rhaos4.9.git3029b1d.el7
0:1.22.1-17.rhaos4.9.git3029b1d.el7
redhat/cri-tools<0:1.22.0-2.el8
0:1.22.0-2.el8
redhat/golang-github-prometheus-promu<0:0.5.0-5.git642a960.el8
0:0.5.0-5.git642a960.el8
redhat/ignition<0:2.12.0-3.rhaos4.9.el8
0:2.12.0-3.rhaos4.9.el8
redhat/etcd<0:3.3.23-7.el8
0:3.3.23-7.el8
redhat/golang-github-vbatts-tar-split<0:0.11.1-6.el8
0:0.11.1-6.el8
redhat/golang-qpid-apache<0:0.32.0-rc1.9.el8
0:0.32.0-rc1.9.el8
redhat/kubevirt<0:2.6.8-211.el7
0:2.6.8-211.el7
redhat/kubevirt<0:4.8.3-251.el7
0:4.8.3-251.el7
redhat/kubevirt<0:2.6.8-211.el8
0:2.6.8-211.el8
redhat/kubevirt<0:4.8.3-251.el8
0:4.8.3-251.el8
IBM Security Guardium Insights<=3.0
Golang Go<1.17
Oracle TimesTen In-Memory Database<21.1.1.1.0
Fedoraproject Fedora=36
redhat/go<1.17.0
1.17.0
Microsoft azl3 python-tensorboard 2.11.0-3<2.16.2-2
2.16.2-2
Microsoft azl3 python-tensorboard 2.16.2-2<2.16.2-2
2.16.2-2
Microsoft cm1 golang 1.16.7-1<1.16.7-1
1.16.7-1

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.26.0-2.el8
  2. Upgrade

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

    Fixed in 0:v1.24.7.redhat1-1.el8
  3. Upgrade

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

    Fixed in 0:2.0.9-3.el8
  4. Upgrade

    Upgrade redhat/servicemesh-prometheus to a version that resolves this vulnerability.

    Fixed in 0:2.14.0-16.el8.1
  5. Upgrade

    Upgrade redhat/servicemesh-proxy to a version that resolves this vulnerability.

    Fixed in 0:2.0.9-3.el8
  6. Upgrade

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

    Fixed in 1.15-golang-0:1.15.14-2.el7_9
  7. Upgrade

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

    Fixed in 0:0.13.1-2.rhaos4.9.el8
  8. Upgrade

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

    Fixed in 0:1.22.1-17.rhaos4.9.git3029b1d.el7
  9. Upgrade

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

    Fixed in 0:1.22.0-2.el8
  10. Upgrade

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

    Fixed in 0:0.5.0-5.git642a960.el8
  11. Upgrade

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

    Fixed in 0:2.12.0-3.rhaos4.9.el8
  12. Upgrade

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

    Fixed in 0:3.3.23-7.el8
  13. Upgrade

    Upgrade redhat/golang-github-vbatts-tar-split to a version that resolves this vulnerability.

    Fixed in 0:0.11.1-6.el8
  14. Upgrade

    Upgrade redhat/golang-qpid-apache to a version that resolves this vulnerability.

    Fixed in 0:0.32.0-rc1.9.el8
  15. Upgrade

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

    Fixed in 0:2.6.8-211.el7
  16. Upgrade

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

    Fixed in 0:4.8.3-251.el7
  17. Upgrade

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

    Fixed in 0:2.6.8-211.el8
  18. Upgrade

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

    Fixed in 0:4.8.3-251.el8
  19. Upgrade

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

    Fixed in 1.17.0
  20. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.16.2-2
  21. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.16.7-1

Event History

Mar 22, 2021
CVE Published
12:00 AM
Aug 7, 2021
CVE Published
via MITRE·04:38 PM
Data Sourced
via MITRE·04:38 PM
Description
Aug 10, 2021
Data Sourced
via Red Hat·02:27 PM
DescriptionSeverityAffected Software
Aug 18, 2021
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the vulnerability ID for this vulnerability?

The vulnerability ID for this vulnerability is CVE-2021-29923.

2

What is the severity level of CVE-2021-29923?

CVE-2021-29923 has a severity level of high.

3

How does CVE-2021-29923 bypass access control?

CVE-2021-29923 bypasses access control based on IP by improperly considering extraneous zero characters at the beginning of an IP address octet.

4

Which software versions are affected by CVE-2021-29923?

Versions up to 1.17.0 of Go, 0:0.26.0-2.el8 of openshift-serverless-clients, 0:v1.24.7.redhat1-1.el8 of kiali, 0:2.0.9-3.el8 of servicemesh, 0:2.14.0-16.el8.1 of servicemesh-prometheus, 0:2.0.9-3.el8 of servicemesh-proxy, 1.15-golang-0:1.15.14-2.el7_9 of go-toolset, 0:0.13.1-2.rhaos4.9.el8 of butane, 0:1.22.1-17.rhaos4.9.git3029b1d.el7 of cri-o, 0:1.22.0-2.el8 of cri-tools, 0:0.5.0-5.git642a960.el8 of golang-github-prometheus-promu, 0:2.12.0-3.rhaos4.9.el8 of ignition, 0:3.3.23-7.el8 of etcd, 0:0.11.1-6.el8 of golang-github-vbatts-tar-split, 0:0.32.0-rc1.9.el8 of golang-qpid-apache, 0:2.6.8-211.el7 and 0:4.8.3-251.el7 of kubevirt, 0:2.6.8-211.el8 and 0:4.8.3-251.el8 of kubevirt, and versions up to 21.1.1.1.0 of Oracle TimesTen In-Memory Database are affected by CVE-2021-29923.

5

How can I fix CVE-2021-29923?

To fix CVE-2021-29923, update to version 1.17.0 or newer of Go, or apply the recommended patches for the affected software.

Company

Resources

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