← Back
CVE-2023-7333
Vulnerability in records-mover (CVE-2023-7333)
Summary
vulnerability in records-mover (CVE-2023-7333). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.6.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-7333** has been found in records-mover.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade records-mover to **1.6.0** or later.
If unsure, ask your IT team or search "records-mover CVE-2023-7333" on the vendor's site.
CVE-2023-7333 (records-mover) — CWE-74 /
Attack vector: local / no user interaction
Patched: `1.6.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-74) exists in records-mover.
📍 Affected scope
records-mover — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.6.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'records-mover' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'records-mover' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `records-mover` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade records-mover to 1.6.0ステージング環境で 1.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
records-mover
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2023-7333
- advisory https://github.com/advisories/GHSA-p3jp-7gj7-h6pr
- package https://github.com/bluelabsio/records-mover
- package https://pypi.org/project/records-mover
- web https://github.com/bluelabsio/records-mover/pull/254
- web https://github.com/bluelabsio/records-mover/commit/3f8383aa89f45d861ca081e3e9fd2cc9d0b5dfaa
- web https://github.com/bluelabsio/records-mover/releases/tag/v1.6.0
- web https://vuldb.com/?ctiid.339566
- web https://vuldb.com/?id.339566