Security readout for executives and security teams
Plain-English summary
CVE-2023-7333 is a SQL injection issue in bluelabsio records-mover, a data movement tool. The reported attack path is local and requires low privileges, limiting broad internet exposure. Successful abuse could affect confidentiality, integrity, and availability at a limited level. The stated fix is upgrading records-mover to version 1.6.0.
Executive priority
Treat as a scheduled remediation item, not an emergency, unless records-mover runs on shared systems with many local users. Upgrade during the next maintenance cycle and confirm where the tool is used in data workflows.
Technical view
The vulnerability affects records-mover up to 1.5.4 in the Table Object Handler, involving an unspecified function. It is classified as CWE-89/CWE-74 with CVSS 3.1 score 5.3: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. The public record names commit 3f8383aa89f45d861ca081e3e9fd2cc9d0b5dfaa and release v1.6.0 as the fix.
Likely exposure
Exposure is most likely on systems where records-mover is installed and usable by local, low-privileged users or automation accounts. The source says the attack must be launched locally, so internet-facing exposure is not indicated by the provided sources.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. Abuse requires local access and privileges. The affected component handles table objects, so data pipeline hosts and environments with database movement workflows are the main review targets.
Researcher notes
The affected function is not identified in the CVE description. The affected-version data includes 1.6.0, while the narrative says 1.6.0 fixes the issue; treat 1.6.0 as fixed based on the patch and release references. Evidence is sufficient for remediation direction but limited for exploitability detail.
Mitigation direction
- Upgrade bluelabsio records-mover to version 1.6.0 or later.
- Prioritize hosts where local users or automation can run records-mover.
- Review vendor release notes and patch commit before deployment.
- Restrict local access to records-mover execution environments where feasible.
Validation and detection
- Inventory installed records-mover versions across developer, ETL, and data hosts.
- Confirm versions 1.5.4 or earlier are upgraded to 1.6.0.
- Check dependency manifests and container images for records-mover usage.
- Verify the patch commit is present if using source 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.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-7333 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
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/RL:O/RC:C
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/RL:O/RC:C1.83.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/RL:O/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- VDB-339566 | bluelabsio records-mover Table Object sql injectionCVE reference · vdb-entry, technical-description
- VDB-339566 | CTI Indicators (IOB, IOC, TTP)CVE reference · signature, permissions-required
- https://github.com/bluelabsio/records-mover/pull/254CVE reference · issue-tracking
- https://github.com/bluelabsio/records-mover/commit/3f8383aa89f45d861ca081e3e9fd2cc9d0b5dfaaCVE reference · patch
- https://github.com/bluelabsio/records-mover/releases/tag/v1.6.0CVE reference · patch
- https://github.com/bluelabsio/records-mover/CVE reference · product
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.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.