OpenofficeApplication · Apache
CVE-2021-41831
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 · uneditedIt is possible for an attacker to manipulate the timestamp of signed documents. All versions of Apache OpenOffice up to 4.1.10 are affected. Users are advised to update to version 4.1.11. See CVE-2021-25634 for the LibreOffice advisory.
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 confidenceApache OpenOffice versions up to 4.1.10 allow an attacker to manipulate the timestamp of signed documents, potentially compromising the integrity verification of document signatures.
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
< 4.1.11CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 Apache OpenOffice versionOpen OpenOffice Writer, go to Help > About OpenOffice to view the version number. Alternatively, check the program's properties or use the command line if available.Affected if The version displayed is 4.1.10 or earlier (versions below 4.1.11 are affected)
-
Identify use of document signing featuresCheck whether you or your users create, sign, or verify signed documents in OpenOffice applications (Writer, Calc, Impress). Look for digital signature indicators or signature panel access in documents.Affected if Signed documents are created or verified using OpenOffice's signature functionality
-
Verify signature integrity checkingOpen a signed document and inspect the signature validation status. Check whether OpenOffice reports signature details and timestamps without errors or warnings.Affected if The vulnerability allows timestamp manipulation, so any signature validation results may be unreliable on affected versions
You are affected if Apache OpenOffice version is below 4.1.11 and you create, sign, or verify digital signatures on documents.
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 · scoped4.1.11
Update Apache OpenOffice to version 4.1.11 to remediate the timestamp manipulation vulnerability in signed documents.
Apache OpenOffice 4.1.11
- Navigate to the official Apache OpenOffice download page at https://www.openoffice.org/download/
- Download Apache OpenOffice version 4.1.11 for your operating system
- Uninstall the current version of Apache OpenOffice from your system
- Run the installer for version 4.1.11 and follow the installation prompts
- After installation, launch Apache OpenOffice and verify the version by clicking Help > About Apache OpenOffice to confirm version 4.1.11 is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Openoffice
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41831 — 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-2021-41831 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