CVE-2013-4582: GitLab vulnerability

CVE-2013-4582: The (1) create_branch, (2) create_tag, (3) import_project, and (4) fork_project functions in lib/gitlab_pro...

The (1) create_branch, (2) create_tag, (3) import_project, and (4) fork_project functions in lib/gitlab_projects.rb in GitLab 5.0 before 5.4.2, Community Edition before 6.2.4, Enterprise Edition before 6.2.1 and gitlab-shell before 1.7.8 allows remote authenticated users to include information from local files into the metadata of a Git repository via the web interface.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 16:45 UTC (UTC+00:00)

Security readout for executives and security teams

Older GitLab versions allowed a logged-in user to cause local file contents from the GitLab server to be written into Git repository metadata through normal project actions. This can turn a code hosting account into a path to sensitive server file exposure. The issue affects very old GitLab and gitlab-shell releases, but any surviving instance should be treated seriously. Exposure is likely limited to organizations still running obsolete self-managed GitLab 5.x, early 6.x, or gitlab-shell before 1.7.8. Internet-facing instances and instances with broad user registration or many project members carry higher concern. Prioritize remediation if any legacy self-managed GitLab remains in service, especially internet-facing systems. The business risk is server-side information exposure by authenticated users, potentially including sensitive operational files. Mitigation focus: Upgrade GitLab and gitlab-shell to the fixed versions or later.; Confirm unsupported legacy GitLab servers have been decommissioned or isolated.; Restrict GitLab access to trusted users until remediation is complete..

Prepared: Jun 6, 2026, 02:49 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-4582 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jan 28, 2020, 15:17 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://www.gitlab.com/2013/11/14/multiple-critical-vulnerabilities-in-gitlab/CVE reference · x_refsource_MISC
https://www.openwall.com/lists/oss-security/2013/11/18/4CVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

GitLabGitLab5.0 before 5.4.2Listed

GitLabGitLab Community Editionbefore 6.2.4Listed

GitLabGitLab Enterprise Editionbefore 6.2.1Listed

GitLabgitlab-shellbefore 1.7.8Listed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.