What is the severity of CVE-2017-1000082?

CVE-2017-1000082 has a medium severity level due to the potential for privilege escalation.

How do I fix CVE-2017-1000082?

To fix CVE-2017-1000082, upgrade to systemd version 234 or later.

What versions of systemd are affected by CVE-2017-1000082?

CVE-2017-1000082 affects systemd versions 233 and earlier, as well as versions between 229 and 234.

What are the potential risks of CVE-2017-1000082?

The risks of CVE-2017-1000082 include unauthorized execution of services with elevated privileges.

Is CVE-2017-1000082 an environment-specific vulnerability?

CVE-2017-1000082 can affect any environment where vulnerable versions of systemd are deployed, regardless of the specific configuration.

Vulnerability/
CVE-2017-1000082

critical

CWE

269

7/7/2017

11/10/2024

CVE-2017-1000082

First published: Fri Jul 07 2017(Updated: )

systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g. "0day"), running the service in question with root privileges rather than the user intended.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
systemd	<=233
systemd	>=229<234

Remedy

http://www.openwall.com/lists/oss-security/2017/07/02/1

Remedy

https://github.com/systemd/systemd/issues/6237

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-1000082?
CVE-2017-1000082 has a medium severity level due to the potential for privilege escalation.
How do I fix CVE-2017-1000082?
To fix CVE-2017-1000082, upgrade to systemd version 234 or later.
What versions of systemd are affected by CVE-2017-1000082?
CVE-2017-1000082 affects systemd versions 233 and earlier, as well as versions between 229 and 234.
What are the potential risks of CVE-2017-1000082?
The risks of CVE-2017-1000082 include unauthorized execution of services with elevated privileges.
Is CVE-2017-1000082 an environment-specific vulnerability?
CVE-2017-1000082 can affect any environment where vulnerable versions of systemd are deployed, regardless of the specific configuration.

agent/references
agent/type
agent/remedy
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/last-modified-date
agent/softwarecombine
agent/author
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-api
source/NVD
agent/software-canonical-lookup
vendor/systemd project
canonical/systemd
version/systemd/233
version/systemd/229

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-2017-1000082?
CVE-2017-1000082 has a medium severity level due to the potential for privilege escalation.
How do I fix CVE-2017-1000082?
To fix CVE-2017-1000082, upgrade to systemd version 234 or later.
What versions of systemd are affected by CVE-2017-1000082?
CVE-2017-1000082 affects systemd versions 233 and earlier, as well as versions between 229 and 234.
What are the potential risks of CVE-2017-1000082?
The risks of CVE-2017-1000082 include unauthorized execution of services with elevated privileges.
Is CVE-2017-1000082 an environment-specific vulnerability?
CVE-2017-1000082 can affect any environment where vulnerable versions of systemd are deployed, regardless of the specific configuration.