What is CVE-2022-1966?

CVE-2022-1966 is a duplicate candidate and users should reference CVE-2022-32250 instead.

What should I do if I come across CVE-2022-1966?

If you come across CVE-2022-1966, please reference CVE-2022-32250 instead.

What is the impact of CVE-2022-1966?

The impact of CVE-2022-1966 is the same as CVE-2022-32250, which should be referenced for more information.

Where can I find more information about CVE-2022-32250?

More information about CVE-2022-32250 can be found at [CVE-2022-32250](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32250).

Is there a fix available for CVE-2022-1966?

Please refer to the mitigation steps provided for CVE-2022-32250 to address this vulnerability.

Vulnerability/
CVE-2022-1966

6/6/2022

7/11/2023

CVE-2022-1966

First published: Mon Jun 06 2022(Updated: )

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-32250. Reason: This candidate is a duplicate of CVE-2022-32250. Notes: All CVE users should reference CVE-2022-32250 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.

Credit: secalert@redhat.com secalert@redhat.com

Affected Software	Affected Version	How to fix

Remedy

If not needed, disable the ability for unprivileged users to create namespaces: $ sudo sysctl -w kernel.unprivileged_userns_clone=0 $ echo kernel.unprivileged_userns_clone=0 | \ sudo tee /etc/sysctl.d/99-disable-unpriv-userns.conf

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is CVE-2022-1966?
CVE-2022-1966 is a duplicate candidate and users should reference CVE-2022-32250 instead.
What should I do if I come across CVE-2022-1966?
If you come across CVE-2022-1966, please reference CVE-2022-32250 instead.
What is the impact of CVE-2022-1966?
The impact of CVE-2022-1966 is the same as CVE-2022-32250, which should be referenced for more information.
Where can I find more information about CVE-2022-32250?
More information about CVE-2022-32250 can be found at [CVE-2022-32250](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32250).
Is there a fix available for CVE-2022-1966?
Please refer to the mitigation steps provided for CVE-2022-32250 to address this vulnerability.

collector/nvd-index
agent/severity
agent/type
agent/first-publish-date
agent/softwarecombine
agent/last-modified-date
collector/launchpad-cve
source/Launchpad
collector/security-tracker-debian
source/Debian
collector/nvd-cve
source/NVD
agent/author
agent/remedy
agent/status
agent/event
agent/description
agent/references
agent/tags
collector/usn-cve
source/Ubuntu
status/rejected

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.