What is the severity of CVE-2016-6854?

CVE-2016-6854 is considered a medium severity vulnerability due to the potential for session hijacking.

How do I fix CVE-2016-6854?

To fix CVE-2016-6854, upgrade Open-Xchange OX Guard to version 2.4.2-rev5 or later.

What impact does CVE-2016-6854 have on users?

CVE-2016-6854 can lead to the execution of malicious scripts in a user's context, posing risks such as session hijacking.

Is CVE-2016-6854 exploitable in all versions of Open-Xchange OX Guard?

CVE-2016-6854 is exploitable in versions of Open-Xchange OX Guard prior to 2.4.2-rev5.

What are the potential consequences of CVE-2016-6854?

The consequences of CVE-2016-6854 include unauthorized access, data theft, and compromise of user sessions.

Vulnerability/
CVE-2016-6854

medium

6.1

CWE

15/12/2016

6/8/2024

CVE-2016-6854: XSS

First published: Thu Dec 15 2016(Updated: )

An issue was discovered in Open-Xchange OX Guard before 2.4.2-rev5. Script code which got injected to a mail with inline PGP signature gets executed when verifying the signature. Malicious script code can be executed within a user's context. This can lead to session hijacking or triggering unwanted actions via the web interface (sending mail, deleting data etc.).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Open-Xchange OX Guard	<=2.4.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6854?
CVE-2016-6854 is considered a medium severity vulnerability due to the potential for session hijacking.
How do I fix CVE-2016-6854?
To fix CVE-2016-6854, upgrade Open-Xchange OX Guard to version 2.4.2-rev5 or later.
What impact does CVE-2016-6854 have on users?
CVE-2016-6854 can lead to the execution of malicious scripts in a user's context, posing risks such as session hijacking.
Is CVE-2016-6854 exploitable in all versions of Open-Xchange OX Guard?
CVE-2016-6854 is exploitable in versions of Open-Xchange OX Guard prior to 2.4.2-rev5.
What are the potential consequences of CVE-2016-6854?
The consequences of CVE-2016-6854 include unauthorized access, data theft, and compromise of user sessions.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/severity
agent/weakness
agent/tags
agent/description
agent/event
agent/first-publish-date
agent/source
vendor/open-xchange
canonical/open-xchange ox guard
version/open-xchange ox guard/2.4.2

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-2016-6854?
CVE-2016-6854 is considered a medium severity vulnerability due to the potential for session hijacking.
How do I fix CVE-2016-6854?
To fix CVE-2016-6854, upgrade Open-Xchange OX Guard to version 2.4.2-rev5 or later.
What impact does CVE-2016-6854 have on users?
CVE-2016-6854 can lead to the execution of malicious scripts in a user's context, posing risks such as session hijacking.
Is CVE-2016-6854 exploitable in all versions of Open-Xchange OX Guard?
CVE-2016-6854 is exploitable in versions of Open-Xchange OX Guard prior to 2.4.2-rev5.
What are the potential consequences of CVE-2016-6854?
The consequences of CVE-2016-6854 include unauthorized access, data theft, and compromise of user sessions.