dbcve.org
OpenofficeApplication · Apache

CVE-2022-47502

HIGH · 7.8 CVSS v3.1 Published 2023-03-24
Fix available
A fix is available. Upgrade to after 4.1.13 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Apache OpenOffice documents can contain links that call internal macros with arbitrary arguments. Several URI Schemes are defined for this purpose. Links can be activated by clicks, or by automatic document events. The execution of such links must be subject to user approval. In the affected versions of OpenOffice, approval for certain links is not requested; when activated, such links could therefore result in arbitrary script execution.

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 confidence

Apache OpenOffice fails to prompt for user approval when certain URI scheme links are activated in documents. These links can invoke internal macros with arbitrary arguments, allowing arbitrary script execution without user consent when the document is opened or a link is clicked.

MitigationUpdate Apache OpenOffice to the patched version. Until then, avoid opening documents from untrusted sources and consider disabling automatic document event processing.

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
OpenofficeApplication
Affected:<= 4.1.13

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
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 checks

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

  1. Check installed Apache OpenOffice version
    Open Apache OpenOffice, then go to Help > About to view the version number. Alternatively, check the program's file properties or look in the installation directory for version information.
    Affected if The installed version is 4.1.13 or lower.
  2. Identify documents with URI scheme links
    Search document directories for Apache OpenOffice files (.odt, .ods, .odp, .docx, .xlsx, .pptx) and inspect them for URI scheme patterns such as 'oneclick:', 'macro:', or similar internal URI handlers. Use grep or a hex editor to find these patterns in file contents.
    Affected if Documents containing suspicious URI scheme links from untrusted sources are present on the system.
  3. Verify macro security settings
    In OpenOffice, go to Tools > Options > Security > Macro Security to check the security level settings for macro execution.
    Affected if Macro security is set to Low or Medium, or if documents are allowed to execute macros without prompting.
  4. Check for automatic document event processing
    Inspect document files for embedded event handlers or check Tools > Customize > Events in OpenOffice to see if automatic event processing is enabled for document actions like OnOpen or OnClose.
    Affected if Automatic document event processing is enabled, allowing documents to execute macros or scripts upon opening.

You are affected if you have Apache OpenOffice version 4.1.13 or lower AND have documents containing malicious URI scheme links that can trigger macro execution without user approval.

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 a release after 4.1.13
Interim mitigation

Update Apache OpenOffice to the patched version. Until then, avoid opening documents from untrusted sources and consider disabling automatic document event processing.

Recommended fix Moderate confidence

Apache OpenOffice 4.1.14 or later stable release

  1. 1. Visit the official Apache OpenOffice website at www.openoffice.org to check for the latest stable release.
  2. 2. Download the most recent version of Apache OpenOffice (version 4.1.14 or later).
  3. 3. Uninstall the current version of Apache OpenOffice from your system.
  4. 4. Install the newly downloaded version of Apache OpenOffice.
  5. 5. Verify the installation was successful by checking the version in the application (Help > About Apache OpenOffice).
Caveat Standard upgrade; ensure you back up any personal documents and macro configurations before uninstalling

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

Fix this in Openoffice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47502 — 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-2022-47502 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