What is the severity of CVE-2008-5155?

CVE-2008-5155 is considered to be moderate in severity due to its potential for local file overwrite and data manipulation.

How do I fix CVE-2008-5155?

To fix CVE-2008-5155, upgrade to a newer version of smsclient that does not utilize temporary files in a vulnerable manner.

Who is affected by CVE-2008-5155?

Local users on systems running smsclient version 2.0.8z are affected by CVE-2008-5155.

What types of attacks are possible with CVE-2008-5155?

CVE-2008-5155 allows for symlink attacks that can overwrite arbitrary files or append data to unintended files.

What are the temporary files involved in CVE-2008-5155?

The temporary files involved in CVE-2008-5155 include /tmp/header.#####, /tmp/body.#####, and /tmp/sms.log.

Vulnerability/
CVE-2008-5155

critical

9.3

CWE

18/11/2008

7/8/2024

CVE-2008-5155

First published: Tue Nov 18 2008(Updated: )

mail2sms.sh in smsclient 2.0.8z allows local users to overwrite arbitrary files via a symlink attack on a (1) /tmp/header.##### or (2) /tmp/body.##### temporary file, or append data to arbitrary files via a symlink attack on the (3) /tmp/sms.log temporary file.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Smsclient	=2.0.8z

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2008-5155?
CVE-2008-5155 is considered to be moderate in severity due to its potential for local file overwrite and data manipulation.
How do I fix CVE-2008-5155?
To fix CVE-2008-5155, upgrade to a newer version of smsclient that does not utilize temporary files in a vulnerable manner.
Who is affected by CVE-2008-5155?
Local users on systems running smsclient version 2.0.8z are affected by CVE-2008-5155.
What types of attacks are possible with CVE-2008-5155?
CVE-2008-5155 allows for symlink attacks that can overwrite arbitrary files or append data to unintended files.
What are the temporary files involved in CVE-2008-5155?
The temporary files involved in CVE-2008-5155 include /tmp/header.#####, /tmp/body.#####, and /tmp/sms.log.

agent/type
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/author
agent/references
agent/weakness
agent/description
agent/first-publish-date
agent/event
agent/source
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/smsclient
canonical/smsclient
version/smsclient/2.0.8z

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-2008-5155?
CVE-2008-5155 is considered to be moderate in severity due to its potential for local file overwrite and data manipulation.
How do I fix CVE-2008-5155?
To fix CVE-2008-5155, upgrade to a newer version of smsclient that does not utilize temporary files in a vulnerable manner.
Who is affected by CVE-2008-5155?
Local users on systems running smsclient version 2.0.8z are affected by CVE-2008-5155.
What types of attacks are possible with CVE-2008-5155?
CVE-2008-5155 allows for symlink attacks that can overwrite arbitrary files or append data to unintended files.
What are the temporary files involved in CVE-2008-5155?
The temporary files involved in CVE-2008-5155 include /tmp/header.#####, /tmp/body.#####, and /tmp/sms.log.