CVE-2023-37219
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTadiran Telecom Composit - CWE-1236: Improper Neutralization of Formula Elements in a CSV File
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCVE-2023-37219 is a CSV Formula Injection vulnerability in Tadiran Telecom Composit. The application fails to properly neutralize formula elements (characters like =, +, -, @, tab, CR) when exporting data to CSV files. When users open the crafted CSV in spreadsheet applications like Excel or LibreOffice, the malicious formulas can execute arbitrary commands or script content on the victim's machine, potentially leading to code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Tadirantele Aeonix installationLocate and verify the presence of Tadiran Telecom Composit or Aeonix application in your environment using system inventory tools or by checking installation directories.Affected if The application is installed and running.
-
Locate CSV export functionalityNavigate through the application interface to identify any features that export data to CSV format, such as reports, call logs, contact lists, or data export utilities.Affected if CSV export feature exists in the application.
-
Prepare test payload with formula charactersCreate or locate data entries containing formula-initiating characters: =, +, -, @, or tab/CR characters. Input these into fields that will be included in a CSV export.Affected if The application allows user-controlled data in exportable fields.
-
Export data to CSV and inspect outputExport the test data to a CSV file, then open the file in a text editor (not a spreadsheet application) to examine the raw CSV content.Affected if The CSV output contains unescaped formula characters (characters not prefixed with a single quote ' or properly double-quoted).
-
Verify escaping of special charactersCheck each formula-initiating character (=, +, -, @) in the CSV output. They should appear as '=..., '+..., '-..., '@... or be enclosed in double quotes to prevent execution.Affected if Any formula-initiating character appears without proper escaping (no leading quote or double-quote wrapper).
If the CSV export contains unescaped formula-initiating characters (=, +, -, @) when viewed in a text editor, the environment is affected by CVE-2023-37219.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper escaping of special characters in CSV exports by prefixing formula-initiating characters (=, +, -, @, tab, CR) with a single quote or applying context-aware encoding; validate and sanitize all user-supplied data before CSV export.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37219 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data