What is the severity of CVE-2013-4489?

CVE-2013-4489 has a high severity rating due to its potential for remote command execution by authenticated users.

How do I fix CVE-2013-4489?

To fix CVE-2013-4489, you should upgrade GitLab to version 5.4.1 or later for the 5.x series, and version 6.2.3 or later for the 6.x series.

Who is affected by CVE-2013-4489?

CVE-2013-4489 affects GitLab versions 5.2.0 to 5.4.0 and 6.0.0 to 6.2.2.

What types of attacks are possible with CVE-2013-4489?

CVE-2013-4489 allows attackers to perform arbitrary command execution through the GitLab code search feature.

Is authentication required to exploit CVE-2013-4489?

Yes, CVE-2013-4489 requires remote authenticated users to exploit the vulnerability.

Vulnerability/
CVE-2013-4489

medium

6.5

17/5/2014

6/8/2024

CVE-2013-4489

First published: Sat May 17 2014(Updated: )

The Grit gem for Ruby, as used in GitLab 5.2 before 5.4.1 and 6.x before 6.2.3, allows remote authenticated users to execute arbitrary commands, as demonstrated by the search box for the GitLab code search feature.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
GitLab	=5.2.0
GitLab	=5.3.0
GitLab	=5.4.0
GitLab	=6.0.0
GitLab	=6.1.0
GitLab	=6.2.0
GitLab	=6.2.1
GitLab	=6.2.2

Remedy

https://www.gitlab.com/2013/11/04/gitlab-ce-6-2-and-5-4-security-release/

Never miss a vulnerability like this again

Reference Links

https://www.gitlab.com/2013/11/04/gitlab-ce-6-2-and-5-4-security-release/

Frequently Asked Questions

What is the severity of CVE-2013-4489?
CVE-2013-4489 has a high severity rating due to its potential for remote command execution by authenticated users.
How do I fix CVE-2013-4489?
To fix CVE-2013-4489, you should upgrade GitLab to version 5.4.1 or later for the 5.x series, and version 6.2.3 or later for the 6.x series.
Who is affected by CVE-2013-4489?
CVE-2013-4489 affects GitLab versions 5.2.0 to 5.4.0 and 6.0.0 to 6.2.2.
What types of attacks are possible with CVE-2013-4489?
CVE-2013-4489 allows attackers to perform arbitrary command execution through the GitLab code search feature.
Is authentication required to exploit CVE-2013-4489?
Yes, CVE-2013-4489 requires remote authenticated users to exploit the vulnerability.

agent/type
agent/references
agent/remedy
agent/author
agent/severity
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
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/5.2.0
version/gitlab/5.3.0
version/gitlab/5.4.0
version/gitlab/6.0.0
version/gitlab/6.1.0
version/gitlab/6.2.0
version/gitlab/6.2.1
version/gitlab/6.2.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-2013-4489?
CVE-2013-4489 has a high severity rating due to its potential for remote command execution by authenticated users.
How do I fix CVE-2013-4489?
To fix CVE-2013-4489, you should upgrade GitLab to version 5.4.1 or later for the 5.x series, and version 6.2.3 or later for the 6.x series.
Who is affected by CVE-2013-4489?
CVE-2013-4489 affects GitLab versions 5.2.0 to 5.4.0 and 6.0.0 to 6.2.2.
What types of attacks are possible with CVE-2013-4489?
CVE-2013-4489 allows attackers to perform arbitrary command execution through the GitLab code search feature.
Is authentication required to exploit CVE-2013-4489?
Yes, CVE-2013-4489 requires remote authenticated users to exploit the vulnerability.