CVE-2022-1996: Authorization Bypass Through User-Controlled Key in emicklei/go-restful

Published Jun 6, 2022
·
Updated

A flaw was found in CORS Filter feature from the go-restful package. When a user inputs a domain which is in AllowedDomains, all domains starting with the same pattern are accepted. This issue could allow an attacker to break the CORS policy by allowing any page to make requests and retrieve data on behalf of users.

Other sources

Authorization Bypass Through User-Controlled Key in GitHub repository emicklei/go-restful prior to v3.8.0.

Affected Software

9 affected componentsFixes available
redhat/openshift-serverless-clients<0:1.3.1-4.el8
0:1.3.1-4.el8
redhat/openshift-gitops-kam<0:1.8.3-6.el8
0:1.8.3-6.el8
redhat/openshift-gitops-kam<0:1.9.0-102.el8
0:1.9.0-102.el8
redhat/go-restful<3.8.0
3.8.0
Go-restful Project Go-restful<2.16.0
Go-restful Project Go-restful>=3.0.0<3.8.0
Fedoraproject Fedora=35
Fedoraproject Fedora=36
IBM Edge Application Manager<=4.5

Event History

Jun 6, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Jun 8, 2022
Data Sourced
via Red Hat·06:51 PM
DescriptionSeverityAffected Software
Aug 20, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2022-1996?

CVE-2022-1996 has been classified with a medium severity level due to its potential impact on CORS policy enforcement.

2

How do I fix CVE-2022-1996?

To remediate CVE-2022-1996, upgrade the go-restful package to version 3.8.0 or later.

3

What products are affected by CVE-2022-1996?

CVE-2022-1996 affects the go-restful package and specific versions of openshift-serverless-clients and openshift-gitops-kam.

4

Can CVE-2022-1996 allow attackers to exploit my application?

Yes, CVE-2022-1996 can allow attackers to bypass CORS policy, enabling malicious actions on behalf of users.

5

Is there a known workaround for CVE-2022-1996?

There are no reported workarounds for CVE-2022-1996; the recommended action is to apply the latest patch.

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