dbcve.org
FedoraOperating system · Fedoraproject

CVE-2024-3044

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 7.6.7.1 / 24.2.3.1 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Unchecked script execution in Graphic on-click binding in affected LibreOffice versions allows an attacker to create a document which without prompt will execute scripts built-into LibreOffice on clicking a graphic. Such scripts were previously deemed trusted but are now deemed untrusted.

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 confidence

A vulnerability in LibreOffice allows maliciously crafted documents to execute built-in scripts through graphic on-click bindings without proper validation. When a user clicks on a graphic element in a specially crafted document, scripts embedded in LibreOffice execute without the expected security prompts, as these scripts were incorrectly classified as trusted.

MitigationUpgrade to patched LibreOffice versions and configure security settings to prompt before executing any scripts or macros, particularly when opening documents from untrusted sources.

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
FedoraOperating system
Affected:= 39
Debian LinuxOperating system
Affected:= 10.0
LibreofficeApplication
Affected:< 7.6.7.1>= 24.2.0.0, < 24.2.3.1

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed LibreOffice version
    On Linux: libreoffice --version or rpm -q libreoffice. On Windows: Check Help > About LibreOffice. On macOS: Check /Applications/LibreOffice.app/Contents/info.plist
    Affected if Version is < 7.6.7.1 OR (>= 24.2.0.0 AND < 24.2.3.1)
  2. Check operating system distribution version
    On Fedora: cat /etc/fedora-release. On Debian: cat /etc/debian_version
    Affected if Running Fedora 39 or Debian 10.0 with LibreOffice installed from default repositories
  3. Examine document security settings
    In LibreOffice, go to Tools > Options > Security > Macro Security. Check the security level setting for macro execution prompts
    Affected if Macro security is set to Low or Medium (rather than High or Very High), allowing scripts to run without prompts
  4. Inspect opened documents for graphic elements with on-click actions
    Open a suspected document, right-click on graphic images, select Properties > Hyperlink > OnClick action. Look for any script or macro assigned
    Affected if Graphics contain assigned on-click scripts that execute without security warnings when clicked

You are affected if LibreOffice version falls within the vulnerable ranges AND macro security settings permit execution without prompts, particularly when opening documents from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.6.7.1 / 24.2.3.1 or later
Fixed in 7.6.7.124.2.3.1
Interim mitigation

Upgrade to patched LibreOffice versions and configure security settings to prompt before executing any scripts or macros, particularly when opening documents from untrusted sources.

Recommended fix High confidence

LibreOffice 7.6.7.1 or later, OR LibreOffice 24.2.3.1 or later

  1. Check current LibreOffice version: Help > About LibreOffice or `libreoffice --version`
  2. For Fedora systems: Run `sudo dnf update libreoffice-*` to install the latest fixed version
  3. For Debian systems: Run `sudo apt update && sudo apt upgrade libreoffice`
  4. Alternatively, download and install fixed versions directly: LibreOffice 7.6.7.1+ or LibreOffice 24.2.3.1+ from www.libreoffice.org
  5. Restart any running LibreOffice instances after upgrade
  6. Verify the fix by opening documents - the graphic on-click binding should now prompt before executing scripts
Caveat Minor point release upgrades typically have minimal breaking changes; users should test critical documents after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3044 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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