Gix-date: gix-date: undefined behavior due to invalid string generation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.12.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
A flaw was found in gix-date. The `gix_date::parse::TimeBuf::as_str` function can generate strings containing invalid non-UTF8 characters. This issue violates the internal safety invariants of the `TimeBuf` component, leading to undefined behavior when these malformed strings are subsequently processed. This could potentially result in application instability or other unforeseen consequences.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- gix-date
fixed in 0.12.0
- openshift-logging/cluster-logging-operator-bundle
Version range not reported
- openshift-logging/cluster-logging-rhel9-operator
Version range not reported
- openshift-logging/eventrouter-rhel9
Version range not reported
- openshift-logging/fluentd-rhel9
Version range not reported
- openshift-logging/log-file-metric-exporter-rhel9
Version range not reported
- openshift-logging/logging-view-plugin-rhel9
Version range not reported
- openshift-logging/vector-rhel9
Version range not reported
- rust
Version range not reported
- rust-toolset:rhel8/rust
Version range not reported
- rust
Version range not reported
- gix-datecrates.io
fixed in 0.12.0
- gix-datecrates.io
From 0.0.0-0 · fixed in 0.12.0