LiveActive security incident?Get immediate response
CVE Record

CVE-2024-55160: GFast between v2 to v3.2 was discovered to contain a SQL injection vulnerability via the OrderBy parameter...

GFast between v2 to v3.2 was discovered to contain a SQL injection vulnerability via the OrderBy parameter at /system/operLog/list.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2024-55160 affects GFast versions v2 through v3.2. A user-controlled OrderBy value in the operation-log list endpoint can influence SQL query construction. The CVE rates this as critical because database confidentiality, integrity, and availability may be impacted. Sources do not identify a patch or confirmed exploitation.

Executive priority

Treat this as urgent for any confirmed GFast v2 through v3.2 deployment. Prioritize internet-facing or broadly accessible administrative interfaces first, then validate patch availability or containment through access controls.

Technical view

The record describes CWE-89 SQL injection in /system/operLog/list through the OrderBy parameter. The CVSS 3.1 vector is 9.8 critical: network reachable, low complexity, no privileges, no user interaction, with high CIA impact. Public references point to GFast os-v3.2 code and a researcher issue, but affected CPE and fix metadata are incomplete.

Likely exposure

Organizations running GFast between v2 and v3.2 are potentially exposed, especially if /system/operLog/list is reachable from untrusted networks. The CVE metadata lists no normalized vendor, product, or CPE, so inventory must verify actual GFast deployments and versions.

Exploitation context

CISA KEV is false in the supplied bundle, and no cited source confirms active exploitation. The vulnerability is still high-risk because the published CVSS vector describes unauthenticated network exploitation and critical database impact.

Researcher notes

Evidence supports the vulnerable parameter and endpoint, but public metadata is thin: vendor/product/CPE are n/a, KEV is false, and no official fixed version is named in the supplied sources. Avoid overstating exploitation until corroborated.

Mitigation direction

  • Identify any GFast deployments and confirm whether versions fall between v2 and v3.2.
  • Check the GFast project and maintainer guidance for an official fix or upgrade path.
  • Restrict access to /system/operLog/list to trusted administrative networks only.
  • If maintaining code, allowlist valid OrderBy columns and avoid raw SQL concatenation.
  • Monitor database and application logs for abnormal operation-log list requests.

Validation and detection

  • Map externally and internally reachable GFast instances before prioritizing remediation.
  • Confirm whether /system/operLog/list is exposed without relying only on asset names.
  • Review local code for OrderBy handling against the referenced os-v3.2 paths.
  • Use non-destructive application security testing in an authorized staging environment.
  • Document whether compensating access controls block untrusted access to the endpoint.
Prepared
Confidence
medium
Sources
6

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.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-55160 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-55160Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.