BugTraq
Open-Xchange Security Advisory 2016-09-13 (2) Sep 13 2016 06:02AM
Martin Heiland (martin heiland lists open-xchange com)
Product: OX Guard
Vendor: OX Software GmbH

Internal reference: 47878 (Bug ID)
Vulnerability type: Cross Site Scripting (CWE-80)
Vulnerable version: 2.4.2 and earlier
Vulnerable component: guard
Report confidence: Confirmed
Solution status: Fixed by Vendor
Fixed version: 2.4.0-rev11, 2.4.2-rev5
Researcher credits: Benjamin Daniel Mussler (@dejavuln)
Vendor notification: 2016-08-03
Solution date: 2016-08-18
Public disclosure: 2016-09-13
CVE reference: CVE-2016-6854
CVSS: 6.5 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)

Vulnerability Details:
Script code which got injected to a mail with inline PGP signature gets executed when verifying the signature.

Risk:
Malicious script code can be executed within a users context. This can lead to session hijacking or triggering unwanted actions via the web interface (sending mail, deleting data etc.).

Steps to reproduce:
1. Add JS code to a mail body
2. Use PGP inline signatures
3. Open the mail in OX App Suite

Solution:
Users should not open mail from untrusted sources. We made sure that the verified content does not get handled in a way that code can get executed. Operators should update to the latest Patch Release.

Internal reference: 47914 (Bug ID)
Vulnerability type: Cross Site Scripting (CWE-80)
Vulnerable version: 2.4.2 and earlier
Vulnerable component: guard
Report confidence: Confirmed
Solution status: Fixed by Vendor
Fixed version: 2.4.0-rev11, 2.4.2-rev5
Researcher credits: secator
Vendor notification: 2016-08-05
Solution date: 2016-08-18
Public disclosure: 2016-09-13
CVE reference: CVE-2016-6853
CVSS: 4.3 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)

Vulnerability Details:
Script code and references to external websites can be injected to the names of PGP public keys. When requesting that key later on using a specific URL, such script code might get executed. In case of injecting external websites, users might get lured into a phishing scheme.

Risk:
Malicious script code can be executed within a users context. This can lead to session hijacking or triggering unwanted actions via the web interface (sending mail, deleting data etc.).

Steps to reproduce:
1. As attacker, create a PGP key with malicious name
2. Get the key ID and create a link which will fetch that key
3. Make the victim call that link

Solution:
Users should not click links from untrusted sources. We now sanitize the returned key and make sure HTML content does not get interpreted by the browser. Operators should update to the latest Patch Release.

Internal reference: 48080 (Bug ID)
Vulnerability type: Cross Site Scripting (CWE-80)
Vulnerable version: 2.4.2 and earlier
Vulnerable component: guard
Report confidence: Confirmed
Solution status: Fixed by Vendor
Fixed version: 2.4.0-rev11, 2.4.2-rev5
Researcher credits: Benjamin Daniel Mussler (@dejavuln)
Vendor notification: 2016-08-15
Solution date: 2016-08-18
Public disclosure: 2016-09-13
CVE reference: CVE-2016-6851
CVSS: 4.3 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)

Vulnerability Details:
Script code can be provided as parameter to the OX Guard guest reader web application. This allows cross-site scripting attacks against arbitrary users since no prior authentication is needed.

Risk:
Malicious script code can be executed within a users context. This can lead to session hijacking or triggering unwanted actions via the web interface (sending mail, deleting data etc.) in case the user has a active session on the same domain already.

Steps to reproduce:
1. As attacker, create a hyperlink with script code included at the "templid" parameter
2. Make the victim open that link

Solution:
Users should not click links from untrusted sources. We now sanitize the returned content for this parameter. Operators should update to the latest Patch Release.

Yours sincerely,
Martin Heiland, Open-Xchange GmbH
-----BEGIN PGP SIGNATURE-----
Version: BCPG v1.53

iQIcBAABCgAGBQJX15aUAAoJEAJhPBDDBiJjgGUP/R09AaYMsHFSuaMTss5vZPYs
eaU9h3JcGgxlbnD3ZmaJtPYrYOMfQisNxAEbF+dICW4HvAuJ1KwDV9VEXXV452u/
uHcnPpevgXUAFifkLnHpH33DyJubcfojrjPM8NicrK+S+ZB8g0o+7Mi87kVdvy0F
RIiWydaXglsBUcz/RRER8nJ7WIXtf8DqbGQ+FS/OK5jd/QFrYFo9e3DbNN77rgDY
TKxrblIO7td7y/8kzFjBrkNzqifN/LbMhHDUeX4creqGdKsL9Yjne8IBuFY1NtRw
005EqwhGmzcZOrZTKfJ+0kUohCp/51/lLy3NEGtgzgXXSao+WvRav5FSATtGMHMQ
R6/pr9KZSloPnx5BvQ2gVO01j33TfqPiNmBDMQXX3P6JXpmB8eI7E3qN/ftxX2eq
t55nV1Rt0JRDqeHaf/gmP7n6ByTTIVld1Czoo6k5Qmj1wmTD1lSfn+/0SocW59Vs
s0/WtLP3b/+mRSrXSrmFwcx9XOry2ka/LYuu4kwR1T3ikodCDo1PpIFi8iiZLhyx
tI569hN2bI9DfjeY84KhcDjNHYRDQdFkHORnGT/seY17sFODlIsj5gIvhlaoSDUa
EzfhjxLv1ZLNz5R+HtMG8X5+Ua/04cK54+ewtAXr4M2vHyxXqSsckU/TAlBPMGBe
FWUMROBWlGa5iyVk/7Kx
=GzZj
-----END PGP SIGNATURE-----

[ reply ]


 

Privacy Statement
Copyright 2010, SecurityFocus