LiveActive security incident?Get immediate response
CVE Record

CVE-2017-1000074: Creolabs Gravity version 1.0 is vulnerable to a stack overflow in the string_repeat() function.

Creolabs Gravity version 1.0 is vulnerable to a stack overflow in the string_repeat() function.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2017-1000074 describes a stack overflow in Creolabs Gravity 1.0, specifically in the string_repeat() function. The public record does not provide severity, CVSS scoring, confirmed impact, or a named fix. Business urgency depends on whether Gravity 1.0 is present and whether untrusted scripts or inputs can reach this function.

Executive priority

Prioritize discovery first. This is not automatically an emergency from the available evidence, but any externally reachable scripting surface using Gravity 1.0 should be reviewed promptly because stack overflows can cause outages and sometimes worse impacts.

Technical view

The CVE record states that Gravity 1.0 is vulnerable to stack overflow in string_repeat(). Available sources do not define preconditions, crash versus code-execution impact, affected platforms, CWE, or remediation details. Treat exposure as implementation-specific until confirmed against local deployments and vendor or project guidance.

Likely exposure

Exposure is most likely where Creolabs Gravity 1.0 is embedded in an application, scripting feature, automation tool, or service that processes user-controlled Gravity code or input reaching string_repeat(). The source bundle does not identify CPEs or downstream products.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. The vulnerability is publicly referenced through a GitHub issue, so defenders should assume technical details may be discoverable, but should not infer exploitation without additional evidence.

Researcher notes

Evidence is sparse: the CVE description and GitHub reference identify the component, version, and vulnerable function only. No CVSS, CWE, exploit status, affected CPE, or fix is provided in the bundle, so conclusions about impact and remediation should remain qualified.

Mitigation direction

  • Inventory applications embedding or shipping Creolabs Gravity 1.0.
  • Check the Gravity project issue and vendor guidance for fixed versions or workarounds.
  • Restrict untrusted users from submitting Gravity scripts or inputs.
  • Isolate affected interpreter use behind least-privilege process controls.
  • Monitor logs for crashes in Gravity-backed features.

Validation and detection

  • Confirm whether Gravity 1.0 exists in source, binaries, containers, or vendor packages.
  • Identify code paths that expose Gravity execution to users or integrations.
  • Review use of string_repeat() in trusted and untrusted script contexts.
  • Check whether a later Gravity version or vendor patch is documented.
  • Record uncertainty where version or reachability cannot be proven.
Prepared
Confidence
medium
Sources
3

Public sources used

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-2017-1000074 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
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
2Source links

CVSS and timeline data

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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