What is the severity of CVE-2023-1708?

CVE-2023-1708 is rated as a high severity vulnerability due to its potential for executing unexpected commands from the victim's clipboard.

How do I fix CVE-2023-1708?

To fix CVE-2023-1708, update your GitLab to version 15.8.5, 15.9.4, or 15.10.1 or later.

Which versions of GitLab are affected by CVE-2023-1708?

CVE-2023-1708 affects all GitLab CE/EE versions prior to 15.8.5, 15.9.4, and 15.10.1.

What impact does CVE-2023-1708 have on users?

CVE-2023-1708 allows attackers to execute unexpected commands on the victim's machine by leveraging non-printable characters copied from the clipboard.

Is there a workaround for CVE-2023-1708 until I can update?

Currently, the only effective measure against CVE-2023-1708 is to update to a secure version of GitLab as there are no documented workarounds.

Vulnerability/
CVE-2023-1708

critical

9.8

CWE

77 94

5/4/2023

2/8/2024

CVE-2023-1708: Command Injection

First published: Wed Apr 05 2023(Updated: )

An issue was identified in GitLab CE/EE affecting all versions from 1.0 prior to 15.8.5, 15.9 prior to 15.9.4, and 15.10 prior to 15.10.1 where non-printable characters gets copied from clipboard, allowing unexpected commands to be executed on victim machine.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=1.0.0<15.8.5
GitLab	>=1.0.0<15.8.5
GitLab	>=15.9.0<15.9.4
GitLab	>=15.9.0<15.9.4
GitLab	=15.10.0
GitLab	=15.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2023-1708?
CVE-2023-1708 is rated as a high severity vulnerability due to its potential for executing unexpected commands from the victim's clipboard.
How do I fix CVE-2023-1708?
To fix CVE-2023-1708, update your GitLab to version 15.8.5, 15.9.4, or 15.10.1 or later.
Which versions of GitLab are affected by CVE-2023-1708?
CVE-2023-1708 affects all GitLab CE/EE versions prior to 15.8.5, 15.9.4, and 15.10.1.
What impact does CVE-2023-1708 have on users?
CVE-2023-1708 allows attackers to execute unexpected commands on the victim's machine by leveraging non-printable characters copied from the clipboard.
Is there a workaround for CVE-2023-1708 until I can update?
Currently, the only effective measure against CVE-2023-1708 is to update to a secure version of GitLab as there are no documented workarounds.

agent/type
agent/references
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/1.0.0
version/gitlab/15.9.0
version/gitlab/15.10.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-2023-1708?
CVE-2023-1708 is rated as a high severity vulnerability due to its potential for executing unexpected commands from the victim's clipboard.
How do I fix CVE-2023-1708?
To fix CVE-2023-1708, update your GitLab to version 15.8.5, 15.9.4, or 15.10.1 or later.
Which versions of GitLab are affected by CVE-2023-1708?
CVE-2023-1708 affects all GitLab CE/EE versions prior to 15.8.5, 15.9.4, and 15.10.1.
What impact does CVE-2023-1708 have on users?
CVE-2023-1708 allows attackers to execute unexpected commands on the victim's machine by leveraging non-printable characters copied from the clipboard.
Is there a workaround for CVE-2023-1708 until I can update?
Currently, the only effective measure against CVE-2023-1708 is to update to a secure version of GitLab as there are no documented workarounds.