What is the severity of CVE-2022-40299?

CVE-2022-40299 is considered a medium severity vulnerability due to its potential to allow local users to gain elevated privileges.

How do I fix CVE-2022-40299?

To fix CVE-2022-40299, upgrade Singular to version 4.3.1 or later.

What type of vulnerability is CVE-2022-40299?

CVE-2022-40299 is a local privilege escalation vulnerability caused by predictable /tmp pathnames.

Who is affected by CVE-2022-40299?

Users of Singular versions prior to 4.3.1 are affected by CVE-2022-40299.

What are the implications of CVE-2022-40299?

The implications of CVE-2022-40299 include the risk of local users executing arbitrary commands with elevated privileges.

Vulnerability/
CVE-2022-40299

high

7.8

CWE

330

9/9/2022

3/8/2024

CVE-2022-40299

First published: Fri Sep 09 2022(Updated: )

In Singular before 4.3.1, a predictable /tmp pathname is used (e.g., by sdb.cc), which allows local users to gain the privileges of other users via a procedure in a file under /tmp. NOTE: this CVE Record is about sdb.cc and similar files in the Singular interface that have predictable /tmp pathnames; this CVE Record is not about the lack of a safe temporary-file creation capability in the Singular language.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Singularity	<4.3.1

Remedy

https://github.com/Singular/Singular/commit/5f28fbf066626fa9c4a8f0e6408c0bb362fb386c

Remedy

https://github.com/Singular/Singular/issues/1137

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-40299?
CVE-2022-40299 is considered a medium severity vulnerability due to its potential to allow local users to gain elevated privileges.
How do I fix CVE-2022-40299?
To fix CVE-2022-40299, upgrade Singular to version 4.3.1 or later.
What type of vulnerability is CVE-2022-40299?
CVE-2022-40299 is a local privilege escalation vulnerability caused by predictable /tmp pathnames.
Who is affected by CVE-2022-40299?
Users of Singular versions prior to 4.3.1 are affected by CVE-2022-40299.
What are the implications of CVE-2022-40299?
The implications of CVE-2022-40299 include the risk of local users executing arbitrary commands with elevated privileges.

agent/type
agent/remedy
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/references
agent/weakness
agent/author
agent/event
agent/description
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/singular
canonical/singularity

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.

Frequently Asked Questions

What is the severity of CVE-2022-40299?
CVE-2022-40299 is considered a medium severity vulnerability due to its potential to allow local users to gain elevated privileges.
How do I fix CVE-2022-40299?
To fix CVE-2022-40299, upgrade Singular to version 4.3.1 or later.
What type of vulnerability is CVE-2022-40299?
CVE-2022-40299 is a local privilege escalation vulnerability caused by predictable /tmp pathnames.
Who is affected by CVE-2022-40299?
Users of Singular versions prior to 4.3.1 are affected by CVE-2022-40299.
What are the implications of CVE-2022-40299?
The implications of CVE-2022-40299 include the risk of local users executing arbitrary commands with elevated privileges.