CVE-2023-6185
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 · uneditedImproper Input Validation vulnerability in GStreamer integration of The Document Foundation LibreOffice allows an attacker to execute arbitrary GStreamer plugins. In affected versions the filename of the embedded video is not sufficiently escaped when passed to GStreamer enabling an attacker to run arbitrary gstreamer plugins depending on what plugins are installed on the target system.
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 · high confidenceLibreOffice's GStreamer integration fails to properly sanitize/validate embedded video filenames before passing them to GStreamer, allowing an attacker to inject arbitrary GStreamer plugin commands through specially crafted filenames.
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 data= 38= 11.0= 12.0>= 7.5.0, < 7.5.9>= 7.6.0, < 7.6.3CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Check installed LibreOffice versionRun ' libreoffice --version ' or ' soffice --version ' to obtain the exact version numberAffected if The version falls within 7.5.0 through 7.5.9, or 7.6.0 through 7.6.3
-
Verify GStreamer support in LibreOfficeCheck if LibreOffice was built with GStreamer support by examining installed packages or running ' libreoffice --help ' for media-related optionsAffected if GStreamer integration is present and available for video handling in the installed LibreOffice build
-
Confirm the operating system versionRun ' cat /etc/os-release ' or ' cat /etc/fedora-release ' to identify the OSAffected if Running Fedora 38, Debian 11.0, or Debian 12.0 with the affected LibreOffice versions installed
-
Identify if video embedding feature is usedInspect documents for embedded video objects or check if the user routinely inserts video files into LibreOffice Writer, Impress, or Calc documentsAffected if The user opens, edits, or creates LibreOffice documents containing embedded or inserted video files from untrusted sources
A user is affected if they are running LibreOffice versions 7.5.0-7.5.9 or 7.6.0-7.6.3 on Fedora 38, Debian 11, or Debian 12, and they open or insert documents containing video files with specially crafted filenames that could be passed to GStreamer.
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.
dbcve · scoped7.5.97.6.3
Update to a patched version of LibreOffice that implements proper input validation and escaping of filenames before passing them to GStreamer, or remove untrusted video files from documents.
LibreOffice 7.5.9 (or later in 7.5.x branch) / LibreOffice 7.6.3 (or later in 7.6.x branch)
- Check your current LibreOffice version by opening LibreOffice and going to Help > About LibreOffice
- For Fedora 38 users: Run 'sudo dnf update' to receive the latest security updates including LibreOffice fixes
- For Debian 11/12 users: Run 'sudo apt update && sudo apt upgrade' to receive the fixed LibreOffice packages
- Alternatively, download LibreOffice 7.5.9 or later (7.5.x branch) from the official LibreOffice website: https://www.libreoffice.org/download/download/
- Alternatively, download LibreOffice 7.6.3 or later (7.6.x branch) from the official LibreOffice website
- After upgrading, verify the version by checking Help > About LibreOffice to confirm you are on version 7.5.9+, 7.6.3+, or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6185 — 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-6185 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