What is the severity of CVE-2007-1856?

CVE-2007-1856 has a moderate severity due to its potential to cause denial of service in Vixie Cron.

How do I fix CVE-2007-1856?

To fix CVE-2007-1856, ensure that Vixie Cron is upgraded to version 4.1-r10 or later, which resolves the insecure permissions issue.

Who is affected by CVE-2007-1856?

CVE-2007-1856 affects users of Vixie Cron versions up to 4.1 on Gentoo Linux installations.

What was the cause of CVE-2007-1856?

CVE-2007-1856 was caused by insecure file permissions that allowed local users to create hard links and disrupt cron operations.

Can CVE-2007-1856 be exploited remotely?

CVE-2007-1856 cannot be exploited remotely as it requires local user access to the system.

Vulnerability/
CVE-2007-1856

low

2.1

CWE

NVD-CWE-Other

18/4/2007

7/8/2024

CVE-2007-1856

First published: Wed Apr 18 2007(Updated: )

Vixie Cron before 4.1-r10 on Gentoo Linux is installed with insecure permissions, which allows local users to cause a denial of service (cron failure) by creating hard links, which results in a failed st_nlink check in database.c.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
Gentoo Linux
paul Vixie Vixie cron	<=4.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2007-1856?
CVE-2007-1856 has a moderate severity due to its potential to cause denial of service in Vixie Cron.
How do I fix CVE-2007-1856?
To fix CVE-2007-1856, ensure that Vixie Cron is upgraded to version 4.1-r10 or later, which resolves the insecure permissions issue.
Who is affected by CVE-2007-1856?
CVE-2007-1856 affects users of Vixie Cron versions up to 4.1 on Gentoo Linux installations.
What was the cause of CVE-2007-1856?
CVE-2007-1856 was caused by insecure file permissions that allowed local users to create hard links and disrupt cron operations.
Can CVE-2007-1856 be exploited remotely?
CVE-2007-1856 cannot be exploited remotely as it requires local user access to the system.

collector/nvd-historical
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/weakness
agent/severity
agent/last-modified-date
agent/references
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gentoo
canonical/gentoo linux
vendor/paul vixie
canonical/paul vixie vixie cron
version/paul vixie vixie cron/4.1

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-2007-1856?
CVE-2007-1856 has a moderate severity due to its potential to cause denial of service in Vixie Cron.
How do I fix CVE-2007-1856?
To fix CVE-2007-1856, ensure that Vixie Cron is upgraded to version 4.1-r10 or later, which resolves the insecure permissions issue.
Who is affected by CVE-2007-1856?
CVE-2007-1856 affects users of Vixie Cron versions up to 4.1 on Gentoo Linux installations.
What was the cause of CVE-2007-1856?
CVE-2007-1856 was caused by insecure file permissions that allowed local users to create hard links and disrupt cron operations.
Can CVE-2007-1856 be exploited remotely?
CVE-2007-1856 cannot be exploited remotely as it requires local user access to the system.