Skip to content
Noroxi
CVE-2024-8640· NVD / CVE Program· CNA GitLab

Improper Neutralization of Special Elements used in a Command ('Command Injection') in GitLab

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.98% (FIRST EPSS); higher than 62% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: GitLab GitLab 17.1.7, 17.2.5, 17.3.2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to GitLab GitLab 17.1.7, 17.2.5, 17.3.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An issue has been discovered in GitLab EE affecting all versions starting from 16.11 prior to 17.1.7, from 17.2 prior to 17.2.5, and from 17.3 prior to 17.3.2. Due to incomplete input filtering, it was possible to inject commands into a connected Cube server.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Sep 12, 2024
Updated
Jun 17, 2026
EPSS
0.9% · 62th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.9%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · GitLab
8.5
0.3 point gap

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-8640

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for gitlab records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gitlabgitlab

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gitlab gitlab16.11.0 and later · before 17.1.7
  • gitlab gitlab17.2.0 and later · before 17.2.5
  • gitlab gitlab17.3.0 and later · before 17.3.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitLab). Independent of NVD's CPE analysis and usually ahead of it.

  • GitLab GitLab

    • 16.11 and later · before 17.1.7affected · semver
    • 17.2 and later · before 17.2.5affected · semver
    • 17.3 and later · before 17.3.2affected · semver

Same product

gitlab: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-22205An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9.KEV
    100Now
  • CVE-2026-85706Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLabKEV
    98Now
  • CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV
    97Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-8631Sep 12, 2024 · Privilege Defined With Unsafe Actions in GitLab
    28Monitor
  • ← EarlierCVE-2024-8635Sep 12, 2024 · Server-Side Request Forgery (SSRF) in GitLab
    26Monitor
  • Later →CVE-2024-8754Sep 12, 2024 · External Control of Critical State Data in GitLab
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
GitLab GitLab17.1.7Vendor (CNA)
GitLab GitLab17.2.5Vendor (CNA)
GitLab GitLab17.3.2Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-1708526 days apartAn 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 wh
    39Monitor
  • CVE-2024-9773196 days apartImproper Neutralization of Special Elements used in a Command ('Command Injection') in GitLab
    32Monitor
  • CVE-2024-8402182 days apartImproper Neutralization of Special Elements used in a Command ('Command Injection') in GitLab
    29Monitor
  • CVE-2019-14944516 days apartAn issue was discovered in GitLab Community and Enterprise Edition before 11.11.8, 12 before 12.0.6, and 12.1 before 12.1.6.
    26Monitor
  • CVE-2024-711021 days apartImproper Neutralization of Special Elements used in a Command ('Command Injection') in GitLab
    25Monitor
  • CVE-2025-6945429 days apartImproper Neutralization of Special Elements used in a Command ('Command Injection') in GitLab
    14Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • CVE-2024-66780 days apartAuthentication Bypass by Spoofing in GitLab
    36Monitor
  • CVE-2024-916429 days apartMissing Authentication for Critical Function in GitLab
    35Monitor
  • CVE-2024-478435 days apartAuthentication Bypass by Primary Weakness in GitLab
    21Monitor
  • CVE-2024-1166875 days apartInsufficient Session Expiration in GitLab
    21Monitor

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records