What is the severity of CVE-2017-5620?

CVE-2017-5620 is classified as a cross-site scripting (XSS) vulnerability.

How do I fix CVE-2017-5620?

To fix CVE-2017-5620, upgrade Zammad to version 1.0.4 or later for 1.0.x, version 1.1.3 or later for 1.1.x, or version 1.2.1 or later for 1.2.x.

What versions of Zammad are affected by CVE-2017-5620?

CVE-2017-5620 affects Zammad versions prior to 1.0.4, 1.1.0-1.1.2, and 1.2.0.

What impact does CVE-2017-5620 have?

CVE-2017-5620 can allow an attacker to execute malicious scripts in the context of the victim's browser.

Is there a workaround for CVE-2017-5620 if I can't upgrade Zammad?

No specific workaround exists for CVE-2017-5620; upgrading to a secure version is the recommended solution.

Vulnerability/
CVE-2017-5620

medium

6.1

CWE

13/3/2017

18/3/2017

CVE-2017-5620: XSS

First published: Mon Mar 13 2017(Updated: )

An XSS issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. Attachments are opened in a new tab instead of getting downloaded. This creates an attack vector of executing code in the domain of the application.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Zammad Zammad	<=1.0.3
Zammad Zammad	=1.1.0
Zammad Zammad	=1.1.1
Zammad Zammad	=1.1.2
Zammad Zammad	=1.2.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5620?
CVE-2017-5620 is classified as a cross-site scripting (XSS) vulnerability.
How do I fix CVE-2017-5620?
To fix CVE-2017-5620, upgrade Zammad to version 1.0.4 or later for 1.0.x, version 1.1.3 or later for 1.1.x, or version 1.2.1 or later for 1.2.x.
What versions of Zammad are affected by CVE-2017-5620?
CVE-2017-5620 affects Zammad versions prior to 1.0.4, 1.1.0-1.1.2, and 1.2.0.
What impact does CVE-2017-5620 have?
CVE-2017-5620 can allow an attacker to execute malicious scripts in the context of the victim's browser.
Is there a workaround for CVE-2017-5620 if I can't upgrade Zammad?
No specific workaround exists for CVE-2017-5620; upgrading to a secure version is the recommended solution.

collector/nvd-index
agent/severity
agent/author
agent/tags
agent/references
agent/weakness
agent/description
agent/type
agent/event
agent/softwarecombine
agent/first-publish-date
agent/last-modified-date
vendor/zammad
canonical/zammad zammad
version/zammad zammad/1.0.3
version/zammad zammad/1.1.0
version/zammad zammad/1.1.1
version/zammad zammad/1.1.2
version/zammad zammad/1.2.0

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-2017-5620?
CVE-2017-5620 is classified as a cross-site scripting (XSS) vulnerability.
How do I fix CVE-2017-5620?
To fix CVE-2017-5620, upgrade Zammad to version 1.0.4 or later for 1.0.x, version 1.1.3 or later for 1.1.x, or version 1.2.1 or later for 1.2.x.
What versions of Zammad are affected by CVE-2017-5620?
CVE-2017-5620 affects Zammad versions prior to 1.0.4, 1.1.0-1.1.2, and 1.2.0.
What impact does CVE-2017-5620 have?
CVE-2017-5620 can allow an attacker to execute malicious scripts in the context of the victim's browser.
Is there a workaround for CVE-2017-5620 if I can't upgrade Zammad?
No specific workaround exists for CVE-2017-5620; upgrading to a secure version is the recommended solution.