What is the severity of CVE-2013-7127?

CVE-2013-7127 is classified as a medium severity vulnerability due to the exposure of cleartext credentials.

How do I fix CVE-2013-7127?

To resolve CVE-2013-7127, users should upgrade to a more secure version of Apple Safari that does not store credentials in cleartext.

Is my system affected by CVE-2013-7127?

If you are using Apple Safari version 6.0.5 on Mac OS X versions 10.7.5 or 10.8.5, your system is affected by CVE-2013-7127.

What kind of information can be obtained from the vulnerability CVE-2013-7127?

CVE-2013-7127 allows local users to access sensitive information, including cleartext credentials stored in the LastSession.plist file.

Are there any workarounds for CVE-2013-7127?

Currently, the best workaround for CVE-2013-7127 is to restrict local user access to the machine or to update the Safari browser to avoid using affected versions.

Vulnerability/
CVE-2013-7127

low

2.1

CWE

310

17/12/2013

29/8/2017

CVE-2013-7127

First published: Tue Dec 17 2013(Updated: )

Apple Safari 6.0.5 on Mac OS X 10.7.5 and 10.8.5 stores cleartext credentials in LastSession.plist, which allows local users to obtain sensitive information by reading this file.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Apple Safari	=6.0.5
macOS Yosemite	=10.7.5
macOS Yosemite	=10.8.5

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2013-7127?
CVE-2013-7127 is classified as a medium severity vulnerability due to the exposure of cleartext credentials.
How do I fix CVE-2013-7127?
To resolve CVE-2013-7127, users should upgrade to a more secure version of Apple Safari that does not store credentials in cleartext.
Is my system affected by CVE-2013-7127?
If you are using Apple Safari version 6.0.5 on Mac OS X versions 10.7.5 or 10.8.5, your system is affected by CVE-2013-7127.
What kind of information can be obtained from the vulnerability CVE-2013-7127?
CVE-2013-7127 allows local users to access sensitive information, including cleartext credentials stored in the LastSession.plist file.
Are there any workarounds for CVE-2013-7127?
Currently, the best workaround for CVE-2013-7127 is to restrict local user access to the machine or to update the Safari browser to avoid using affected versions.

agent/references
agent/severity
agent/first-publish-date
agent/last-modified-date
agent/softwarecombine
agent/tags
agent/event
agent/type
collector/nvd-index
agent/software-canonical-lookup-request
agent/description
agent/weakness
agent/author
vendor/apple
canonical/apple safari
version/apple safari/6.0.5
canonical/macos yosemite
version/macos yosemite/10.7.5
version/macos yosemite/10.8.5

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-2013-7127?
CVE-2013-7127 is classified as a medium severity vulnerability due to the exposure of cleartext credentials.
How do I fix CVE-2013-7127?
To resolve CVE-2013-7127, users should upgrade to a more secure version of Apple Safari that does not store credentials in cleartext.
Is my system affected by CVE-2013-7127?
If you are using Apple Safari version 6.0.5 on Mac OS X versions 10.7.5 or 10.8.5, your system is affected by CVE-2013-7127.
What kind of information can be obtained from the vulnerability CVE-2013-7127?
CVE-2013-7127 allows local users to access sensitive information, including cleartext credentials stored in the LastSession.plist file.
Are there any workarounds for CVE-2013-7127?
Currently, the best workaround for CVE-2013-7127 is to restrict local user access to the machine or to update the Safari browser to avoid using affected versions.