Skip to content
Emerging threatsMedium

CVE-2013-4490Gitlab Vulnerability

The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x before 6.2.3, allows remote authenticated users to execute arbitrary commands via shell metacharacters in the public key.

Published May 13, 2014 · Updated Aug 6, 2024

Key Facts

Routine patching
  • CVE-2013-4490 is a medium-severity vulnerability (CVSS 6.5 v2) affecting Gitlab, Gitlab-Shell.
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 42% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Gitlab-Shell 1.7.2, Gitlab 0.
  • Brandefense priority: routine patching, as no exploitation is known and its severity is moderate or low.

Scores

CVSS v2

6.5

AV:N/AC:L/Au:S/C:P/I:P/A:P

EPSS (30-day exploit likelihood)

42%

Higher than 98.6% of all scored CVEs

Exploit maturity

Weaponized

ATLAS score

48/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Weaponized

Public exploit code

2

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Description

The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x before 6.2.3, allows remote authenticated users to execute arbitrary commands via shell metacharacters in the public key.

Affected Products

22 affected entries in total
ProductAffected versionsFixed in
GitlabGitlab5.0.0, 5.0.1, 5.1.0, 5.2.0, 5.3.0, 5.4.0, 6.0.0, 6.1.00
Gitlab-ShellGitlab1.0.4, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.01.7.2

Patched Releases

Gitlab-Shell

1.7.2

Timeline

  1. Publicly disclosed

    May 13, 2014

  2. Last updated

    Aug 6, 2024

FAQ

Common Questions.

Is CVE-2013-4490 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.