Microsoft Word 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.

Last Year

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.

Version

200346
200738
200238
201631
200031

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix125
Temporary Fix0
Workaround0
Unavailable1
Not Defined20

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

High6
Functional1
Proof-of-Concept44
Unproven24
Not Defined71

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
Local11
Adjacent5
Network130

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
Low5
None140

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
Required57
None89

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.

Last Year

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
≤30
≤42
≤57
≤610
≤722
≤855
≤93
≤1047

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
≤30
≤43
≤58
≤611
≤752
≤825
≤920
≤1027

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
≤30
≤43
≤59
≤67
≤743
≤835
≤92
≤1047

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
≤65
≤70
≤817
≤914
≤100

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
≤20
≤30
≤40
≤50
≤62
≤71
≤85
≤90
≤101

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
≤72
≤811
≤90
≤102

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

<1k0
<2k0
<5k4
<10k15
<25k67
<50k44
<100k4
≥100k12

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

<1k126
<2k3
<5k9
<10k4
<25k4
<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.

Last Year

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 Versions (27): 3.0, 6.0, 97, 98, 365 Apps for Enterprise, 365 ProPlus, 2000, 2001, 2002, 2003, 2003 SP3, 2004, 2007, 2007 SP3, 2010, 2010 SP1, 2010 SP2, 2011, 2013, 2013 RT SP1, 2013 SP1, 2016, 2019, 2021, LTSC 2021, Office Online Server, SP3

Link to Product Website: https://www.microsoft.com/

Software Type: Office Suite Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
02/13/20247.36.7Microsoft Office/Word Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.04CVE-2024-21379
02/13/20247.36.7Microsoft Excel/Office/PowerPoint/Publisher/Visio/Word/Skype Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2024-20673
09/12/20237.06.4Microsoft Word Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2023-36762
09/12/20235.25.1Microsoft Word information disclosure$0-$5k$0-$5kHighOfficial Fix0.04CVE-2023-36761
07/11/20238.88.0Microsoft Word Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.03CVE-2023-33150
02/14/20238.07.1Microsoft Word wwlib Remote Code Execution$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.03CVE-2023-21716
11/08/20225.14.7Microsoft Word information disclosure$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2022-41103
11/08/20227.36.7Microsoft Word Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2022-41061
11/08/20225.14.7Microsoft Word information disclosure$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2022-41060
01/11/20227.36.7Microsoft Word Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2022-21842
09/14/20217.06.1Microsoft Word Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.04CVE-2021-38656
07/13/20217.06.1Microsoft Word Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2021-34452
05/11/20217.06.1Microsoft Office/Word Graphics Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2021-31180
04/13/20217.06.1Microsoft Word/Office/SharePoint Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2021-28453
03/09/20214.94.5Microsoft Word input validation$0-$5k$0-$5kProof-of-ConceptOfficial Fix0.00CVE-2021-24104
01/12/20217.36.4Microsoft Word Remote Code Execution$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2021-1716
01/12/20217.36.4Microsoft Word out-of-bounds write$5k-$25k$0-$5kUnprovenOfficial Fix0.05CVE-2021-1715
10/13/20207.46.6Microsoft Word LNK File 7pk security$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.00CVE-2020-16933
08/11/20204.94.7Microsoft Word information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-1502
08/11/20204.94.7Microsoft Word information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix0.05CVE-2020-1583
08/11/20204.94.7Microsoft Word information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-1503
06/09/20207.57.2Microsoft Word input validation$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-1223
04/14/20207.06.7Microsoft Office/SharePoint/Word memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-0980
04/14/20207.57.2Microsoft Office input validation$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-0760
08/13/20197.06.7Microsoft Word memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2019-1205

121 more entries are not shown

more entries by Microsoft

Do you want to use VulDB in your project?

Use the official API to access entries easily!