Security readout for executives and security teams
Plain-English summary
CVE-2017-1000072 describes a double-free memory error in Creolabs Gravity version 1.0. In business terms, software using this component could crash or behave unpredictably if the vulnerable code path is reached. The public source bundle does not provide CVSS scoring, confirmed exploitation, or a named fixed version.
Executive priority
Prioritize investigation if Gravity is embedded in externally reachable services or automation. Otherwise, handle through dependency hygiene and monitoring. The missing severity score and fix details make confirmation of actual use the key first step.
Technical view
The CVE states that Gravity 1.0 has a double free in gravity_value, potentially allowing modification of unexpected memory locations. No CWE, CVSS vector, affected CPEs, exploit details, or patch information are provided in the bundle. Impact depends on whether an application embeds this Gravity version and exposes relevant inputs.
Likely exposure
Exposure is likely limited to environments that directly use or embed Creolabs Gravity version 1.0. Risk is higher where untrusted users, files, or scripts can reach Gravity value-handling logic. The source bundle does not identify downstream products or package identifiers.
Exploitation context
The provided data does not support a claim of active exploitation. CISA KEV status is false, and the only listed confirmation reference is a GitHub issue. Public exploitability, real-world abuse, and prerequisites are not established by the provided sources.
Researcher notes
The evidence is sparse: description, version, fault class, and one confirmation issue. Avoid broad claims beyond Gravity 1.0. Focus validation on code presence, reachability, trust boundary, and whether project maintainers documented a fix after the referenced issue.
Mitigation direction
- Inventory applications and dependencies for Creolabs Gravity version 1.0 usage.
- Check the referenced project issue and vendor guidance for fix status.
- Restrict untrusted access to Gravity script or input processing paths.
- Apply an upstream fix only if the project identifies a corrected release.
- Use sandboxing or isolation where Gravity processes external content.
Validation and detection
- Search SBOMs, lockfiles, vendored code, and build scripts for Gravity.
- Confirm whether version 1.0 or vulnerable gravity_value code is present.
- Map whether external users can influence Gravity input or scripts.
- Review crash reports for memory corruption symptoms in Gravity components.
- Track the referenced GitHub issue for remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2017-1000072 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
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://github.com/marcobambini/gravity/issues/123CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.