What is the severity of CVE-2014-5449?

CVE-2014-5449 has a medium severity rating due to the potential exposure of sensitive information.

How do I fix CVE-2014-5449?

To fix CVE-2014-5449, restrict the permissions of the tmp directory to ensure that sensitive session data is not world-readable.

What products are affected by CVE-2014-5449?

CVE-2014-5449 affects Zarafa WebAccess 4.1 and the Zarafa WebApp due to insecure file permissions.

Can local users exploit CVE-2014-5449?

Yes, local users can exploit CVE-2014-5449 to read sensitive session data due to world-readable permissions.

Is CVE-2014-5449 still a concern today?

Yes, CVE-2014-5449 remains a concern if vulnerable versions of Zarafa software are still in use without appropriate security measures.

Vulnerability/
CVE-2014-5449

low

2.1

CWE

200

20/10/2014

8/9/2017

CVE-2014-5449: Infoleak

First published: Mon Oct 20 2014(Updated: )

Zarafa WebAccess 4.1 and WebApp uses world-readable permissions for the files in their tmp directory, which allows local users to obtain sensitive information by reading temporary session data.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Zarafa WebAccess	=4.1
Zarafa WebApp

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2014-5449?
CVE-2014-5449 has a medium severity rating due to the potential exposure of sensitive information.
How do I fix CVE-2014-5449?
To fix CVE-2014-5449, restrict the permissions of the tmp directory to ensure that sensitive session data is not world-readable.
What products are affected by CVE-2014-5449?
CVE-2014-5449 affects Zarafa WebAccess 4.1 and the Zarafa WebApp due to insecure file permissions.
Can local users exploit CVE-2014-5449?
Yes, local users can exploit CVE-2014-5449 to read sensitive session data due to world-readable permissions.
Is CVE-2014-5449 still a concern today?
Yes, CVE-2014-5449 remains a concern if vulnerable versions of Zarafa software are still in use without appropriate security measures.

collector/nvd-index
agent/author
agent/severity
agent/references
agent/weakness
agent/tags
agent/type
agent/event
agent/description
agent/last-modified-date
vendor/zarafa
canonical/zarafa webaccess
version/zarafa webaccess/4.1
canonical/zarafa webapp

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-2014-5449?
CVE-2014-5449 has a medium severity rating due to the potential exposure of sensitive information.
How do I fix CVE-2014-5449?
To fix CVE-2014-5449, restrict the permissions of the tmp directory to ensure that sensitive session data is not world-readable.
What products are affected by CVE-2014-5449?
CVE-2014-5449 affects Zarafa WebAccess 4.1 and the Zarafa WebApp due to insecure file permissions.
Can local users exploit CVE-2014-5449?
Yes, local users can exploit CVE-2014-5449 to read sensitive session data due to world-readable permissions.
Is CVE-2014-5449 still a concern today?
Yes, CVE-2014-5449 remains a concern if vulnerable versions of Zarafa software are still in use without appropriate security measures.