Word Processing Software Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Vendor

Identifying all affected vendors is a good starting point for an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Product

Microsoft Word129
vim123
Vim23
GNU Emacs18
VIM14

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix303
Temporary Fix0
Workaround0
Unavailable4
Not Defined31

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High3
Functional1
Proof-of-Concept62
Unproven20
Not Defined252

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local36
Adjacent6
Network296

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High1
Low18
None319

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required188
None150

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤31
≤45
≤522
≤646
≤781
≤8116
≤99
≤1058

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤31
≤47
≤524
≤649
≤7120
≤877
≤927
≤1033

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤31
≤46
≤536
≤627
≤7152
≤852
≤96
≤1058

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤40
≤50
≤617
≤70
≤852
≤914
≤108

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤21
≤30
≤41
≤51
≤66
≤727
≤884
≤914
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤51
≤62
≤71
≤87
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k16
<2k37
<5k148
<10k18
<25k54
<50k47
<100k5
≥100k13

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k296
<2k14
<5k8
<10k12
<25k8
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (45): Abisource Community Abiword, AbiWord, Apple iWork, Apple Keynote, Apple Numbers, Apple Pages, Corel WordPerfect, Daiki Ueno Liece Emacs IRC Client, Elixir VIM Plugin, Emacs, emacs-jabber, Emacspeak, GNU Emacs, GNU emacs, JetBrains VIM Plugin, Microsoft 365 Apps for Enterprise, Microsoft Excel, Microsoft Office, Microsoft Office Compability Pack, Microsoft Office Compatibility Pack, Microsoft Office Web Apps, Microsoft Office Web Apps Server, Microsoft Outlook, Microsoft Powerpoint, Microsoft SharePoint, Microsoft Sharepoint, Microsoft SharePoint Enterprise Server, Microsoft SharePoint Server, Microsoft Word, Microsoft WordPad, Microsoft WordPerfect, Microsoft Wordperfect Converter, Microsoft Word 2003, Microsoft Word Viewer, Neovim, SourceForge Wordperfect Document Importer-exporter, vim, Vim, VIM, VIM GVim, vim netrw, Vim tar.vim, Vim zipPlugin.vim, XEmacs, Xemacs

PublishedBaseTempVulnerabilityProductExpRemCTICVE
12/06/20227.06.9vim use after freevimNot DefinedOfficial Fix0.25CVE-2022-4292
12/06/20227.06.8vim floating point comparison with incorrect operatorvimNot DefinedOfficial Fix0.32CVE-2022-4293
12/03/20225.25.0vim heap-based overflowvimNot DefinedOfficial Fix0.15CVE-2022-3491
12/02/20227.06.9vim heap-based overflowvimNot DefinedOfficial Fix0.13CVE-2022-3520
12/02/20227.06.9vim use after freevimNot DefinedOfficial Fix0.02CVE-2022-3591
11/28/20225.04.8GNU Emacs ctags etags.c os command injectionEmacsNot DefinedOfficial Fix0.06CVE-2022-45939
11/25/20226.86.6vim heap-based overflowvimNot DefinedOfficial Fix0.04CVE-2022-4141
11/08/20224.94.3Microsoft Word information disclosureWordUnprovenOfficial Fix0.04CVE-2022-41103
11/08/20227.06.1Microsoft Word Remote Code ExecutionWordUnprovenOfficial Fix0.02CVE-2022-41061
11/08/20224.94.3Microsoft Word information disclosureWordUnprovenOfficial Fix0.03CVE-2022-41060
10/26/20225.85.8vim autocmd quickfix.c qf_update_buffer use after freevimNot DefinedOfficial Fix0.07CVE-2022-3705
09/29/20227.06.9vim use after freevimNot DefinedOfficial Fix0.04CVE-2022-3352
09/29/20225.55.4vim null pointer dereferencevimNot DefinedOfficial Fix0.05CVE-2022-1725
09/28/20227.37.2vim stack-based overflowvimNot DefinedOfficial Fix0.03CVE-2022-3324
09/26/20227.37.2vim use after freevimNot DefinedOfficial Fix0.00CVE-2022-3297
09/26/20227.37.2vim stack-based overflowvimNot DefinedOfficial Fix0.04CVE-2022-3296
09/24/20225.55.5vim null pointer dereferencevimNot DefinedOfficial Fix0.04CVE-2022-3278
09/23/20227.37.2vim use after freevimNot DefinedOfficial Fix0.06CVE-2022-3256
09/19/20227.37.2vim use after freevimNot DefinedOfficial Fix0.02CVE-2022-3235
09/18/20227.37.2vim heap-based overflowvimNot DefinedOfficial Fix0.03CVE-2022-3234
09/09/20225.35.2vim null pointer dereferencevimNot DefinedOfficial Fix0.05CVE-2022-3153
09/07/20227.06.9vim use after freevimNot DefinedOfficial Fix0.05CVE-2022-3134
09/03/20227.37.2vim use after freevimNot DefinedOfficial Fix0.00CVE-2022-3099
08/31/20227.37.2vim use after freevimNot DefinedOfficial Fix0.03CVE-2022-3037
08/28/20227.37.2vim use after freevimNot DefinedOfficial Fix0.03CVE-2022-3016

313 more entries are not shown

Want to stay up to date on a daily basis?

Enable the mail alert feature now!