Security readout for executives and security teams
Plain-English summary
CVE-2017-9432 is a memory corruption flaw in older libstaroffice code. A specially malformed document could cause an out-of-bounds write during parsing. The public bundle does not provide a severity score or evidence of active exploitation, but document parsing bugs can matter where untrusted files are processed automatically.
Executive priority
Treat this as a targeted hygiene item for document-processing environments, not an emergency from current evidence. Prioritize it where untrusted files are parsed at scale or automatically.
Technical view
libstaroffice before 2017-04-07 contains a stack-based buffer overflow related to DatabaseName::read in lib/StarWriterStruct.cxx. The CVE describes an out-of-bounds write. References include an upstream commit and an OSS-Fuzz issue, but no CVSS vector, CWE mapping, or downstream affected product list is provided.
Likely exposure
Exposure is limited to systems or applications using libstaroffice versions before 2017-04-07, especially where the library parses untrusted office documents. The source bundle does not identify downstream products or packages.
Exploitation context
The sources do not report active exploitation, and CISA KEV is false. The OSS-Fuzz reference indicates the issue was found through fuzzing. No public exploit status is established in the provided evidence.
Researcher notes
Evidence is sparse: the CVE record names the vulnerable function and date boundary, while references point to an upstream commit and OSS-Fuzz issue. No CVSS, CWE, affected downstream products, or exploitation confirmation is included.
Mitigation direction
- Upgrade libstaroffice to a version including the 2017-04-07 fix.
- Review the upstream commit and vendor packaging advisories for exact fixed builds.
- Restrict automated processing of untrusted documents until affected instances are updated.
- Check applications that embed libstaroffice rather than only system packages.
Validation and detection
- Inventory installed and bundled libstaroffice versions.
- Confirm no deployed build predates 2017-04-07.
- Review dependency manifests and container images for embedded copies.
- Verify document-processing services do not use obsolete libstaroffice builds.
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-9432 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/fosnola/libstaroffice/commit/2d6253c7a692a3d92785dd990fce7256ea05e794CVE reference · x_refsource_MISC
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1029CVE reference · x_refsource_MISC
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.