What is the severity of CVE-2012-1174?

CVE-2012-1174 has been classified with a moderate severity level due to its potential for local attacker exploitation.

How do I fix CVE-2012-1174?

To fix CVE-2012-1174, it is recommended to update the systemd package to the latest version that addresses this vulnerability.

Who is affected by CVE-2012-1174?

Users of systemd version 43 are affected by CVE-2012-1174.

What type of attack can be executed using CVE-2012-1174?

CVE-2012-1174 can be exploited through symbolic link attacks that target user session records during logout.

When was CVE-2012-1174 discovered?

CVE-2012-1174 was reported in 2012.

Vulnerability/
CVE-2012-1174

low

3.3

CWE

362

14/3/2012

12/7/2012

6/8/2024

CVE-2012-1174: Race Condition

First published: Wed Mar 14 2012(Updated: )

A TOCTOU race condition was found in the way the systemd-logind login manager of the systemd, a system and service manager for Linux, performed removal of particular records related with user session upon user logout. A local attacker could use this flaw to conduct symbolic link attacks, potentially leading to removal of arbitrary system file.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
systemd	=43

Remedy

http://cgit.freedesktop.org/systemd/systemd/commit/?id=5ebff5337594d690b322078c512eb222d34aaa82

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2012-1174?
CVE-2012-1174 has been classified with a moderate severity level due to its potential for local attacker exploitation.
How do I fix CVE-2012-1174?
To fix CVE-2012-1174, it is recommended to update the systemd package to the latest version that addresses this vulnerability.
Who is affected by CVE-2012-1174?
Users of systemd version 43 are affected by CVE-2012-1174.
What type of attack can be executed using CVE-2012-1174?
CVE-2012-1174 can be exploited through symbolic link attacks that target user session records during logout.
When was CVE-2012-1174 discovered?
CVE-2012-1174 was reported in 2012.

agent/type
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/author
agent/references
agent/description
agent/remedy
agent/event
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2012-1174
agent/weakness
agent/trending
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/linux
canonical/systemd
version/systemd/43

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-2012-1174?
CVE-2012-1174 has been classified with a moderate severity level due to its potential for local attacker exploitation.
How do I fix CVE-2012-1174?
To fix CVE-2012-1174, it is recommended to update the systemd package to the latest version that addresses this vulnerability.
Who is affected by CVE-2012-1174?
Users of systemd version 43 are affected by CVE-2012-1174.
What type of attack can be executed using CVE-2012-1174?
CVE-2012-1174 can be exploited through symbolic link attacks that target user session records during logout.
When was CVE-2012-1174 discovered?
CVE-2012-1174 was reported in 2012.