Security readout for executives and security teams
Plain-English summary
CVE-2022-31321 describes weak validation of a folder name input in Bolt 5.1.7. A crafted input may let an attacker enumerate directories or trigger denial of service. The public record does not provide severity, CVSS, fixed version, or detailed affected-product metadata.
Executive priority
Treat as a verification item rather than an emergency based on current evidence. Prioritize if Bolt 5.1.7 is internet-facing, business-critical, or exposed to untrusted users.
Technical view
The issue is tied to the foldername parameter in Bolt 5.1.7. Incorrect input validation can expose directory enumeration behavior or service disruption through crafted input. The supplied sources do not identify a CWE, endpoint, authentication requirement, patch, or precise operational preconditions.
Likely exposure
Potential exposure is limited to environments running Bolt 5.1.7 where the affected foldername handling is reachable. The source data does not confirm whether exposure requires authentication or a specific interface.
Exploitation context
CISA KEV status is false in the provided bundle, and no cited source states active exploitation. Public evidence only supports a vulnerability description, not observed exploitation or weaponized use.
Researcher notes
The public data is sparse: no CVSS, CWE, exploit status, patch reference, or detailed affected CPEs are provided. Avoid assumptions beyond Bolt 5.1.7 and the foldername validation issue.
Mitigation direction
- Inventory systems for Bolt 5.1.7 deployments.
- Check Bolt vendor or maintainer guidance for fixed versions or mitigations.
- Restrict access to Bolt administrative or file-handling functions where feasible.
- Monitor application logs for unusual foldername-related errors or repeated probing.
Validation and detection
- Confirm whether any deployed Bolt instance is version 5.1.7.
- Identify routes or features that accept foldername input.
- Review logs for directory enumeration attempts or denial-of-service symptoms.
- Document whether the affected functionality is internet-facing or authenticated only.
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-2022-31321 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.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Accenture/AARO-Bugs/blob/master/AARO-CVE-List.mdCVE reference, mitre
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.