Mit Kerberos 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

5-1.822
5-1.520
5-1.619
5-1.419
5-1.718

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 Fix114
Temporary Fix0
Workaround0
Unavailable0
Not Defined28

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

High0
Functional0
Proof-of-Concept49
Unproven17
Not Defined76

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
Adjacent10
Network121

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
High0
Low43
None99

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
Required0
None142

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
≤47
≤511
≤636
≤710
≤840
≤97
≤1031

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
≤411
≤520
≤626
≤736
≤815
≤925
≤109

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
≤49
≤513
≤633
≤711
≤839
≤96
≤1031

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
≤44
≤51
≤62
≤76
≤84
≤91
≤103

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
≤60
≤70
≤81
≤90
≤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
≤50
≤60
≤70
≤80
≤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

<1k0
<2k0
<5k18
<10k44
<25k43
<50k36
<100k1
≥100k0

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

<1k125
<2k3
<5k6
<10k5
<25k3
<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 (139): 1.0, 1.0.8, 1.0.8mit, 1.1, 1.2, 1.2.2.beta1, 1.3, 1.4, 1.5, 1.6, 1.6.3, 1.6.3 Kdc, 1.7, 1.8, 1.9, 1.10, 1.10.1, 1.10.2, 1.10.3, 1.10.4, 1.10.6, 1.11, 1.11.3, 1.12, 1.13, 1.13.1, 1.13.2, 1.13.3, 1.13.4, 1.14, 1.14.1, 1.14.2, 1.15, 1.15.1, 1.15.2, 1.16, 1.17, 1.17.1, 1.18, 1.18.1, 1.18.2, 1.18.3, 1.18.4, 1.19, 1.19.1, 1.19.2, 1.20, 1.20.1, 1.21, 1.21.1, 1.21.2, 4, 4.0, 5, 5 1.0, 5 1.0.6, 5 1.1, 5 1.1.1, 5 1.2, 5 1.3.3, 5 1.13, 5-1.0, 5-1.1, 5-1.2, 5-1.2.1, 5-1.2.2, 5-1.2.3, 5-1.2.4, 5-1.2.5, 5-1.2.6, 5-1.2.7, 5-1.2.8, 5-1.3, 5-1.3.1, 5-1.3.2, 5-1.3.3, 5-1.3.4, 5-1.3.5, 5-1.3.6, 5-1.4, 5-1.4.1, 5-1.4.2, 5-1.4.3, 5-1.4.4, 5-1.5, 5-1.5.1, 5-1.5.2, 5-1.5.3, 5-1.5.4, 5-1.6, 5-1.6.1, 5-1.6.2, 5-1.6.3, 5-1.7, 5-1.7.1, 5-1.8, 5-1.8.1, 5-1.8.2, 5-1.8.3, 5-1.8.4, 5-1.8.5, 5-1.8.6, 5-1.9, 5-1.9.1, 5-1.9.2, 5-1.9.3, 5-1.9.4, 5-1.10, 5-1.10.1, 5-1.10.2, 5-1.10.3, 5-1.10.4, 5-1.10.5, 5-1.10.6, 5-1.10.7, 5-1.11, 5-1.11.1, 5-1.11.2, 5-1.11.3, 5-1.11.4, 5-1.11.5, 5-1.12, 5-1.12.1, 5-1.12.2, 5-1.13, 5-1.13.1, 5-1.14, 5-appl 1.0.1, 5.1, 5.1.1, 5.1.2, 5.1.3, 5.1.4, 5.1.5, 5.1.6, 5.1.7, 5.1.8, 5.1.9, 5.18

Link to Product Website: http://www.mit.edu/

Software Type: Network Authentication Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
06/28/20247.37.2MIT Kerberos 5 GSS Message Token Privilege Escalation$5k-$25k$0-$5kNot DefinedOfficial Fix0.07CVE-2024-37371
06/28/20246.56.4MIT Kerberos 5 GSS Message Token Privilege Escalation$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2024-37370
02/26/20245.55.4MIT Kerberos 5 k5sealv3.c memory leak$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2024-26461
02/26/20243.53.4MIT Kerberos 5 pmap_rmt.c memory leak$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2024-26458
02/26/20243.53.4MIT Kerberos 5 ndr.c memory leak$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2024-26462
08/16/20237.17.0MIT Kerberos 5 do_tgs_req.c improper authorization$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2023-39975
08/08/20235.45.3MIT Kerberos 5 kadmind kadm_rpc_xdr.c _xdr_kadm5_principal_ent_rec uninitialized pointer$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-36054
08/23/20213.53.4MIT Kerberos 5 Key Distribution Center do_tgs_req.c null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-37750
07/23/20214.34.1MIT Kerberos 5 Key Distribution Center kdc_preauth_ec.c ec_verify null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-36222
11/06/20205.55.3MIT Kerberos 5 ASN.1 asn1_encode.c recursion$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-28196
12/26/20185.15.0MIT Kerberos input validation$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2018-20217
03/06/20185.14.9MIT Kerberos 5 kadmin ldap injection$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2018-5730
03/06/20184.54.4MIT Kerberos 5 kadmin null pointer dereference$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2018-5729
01/16/20185.45.4MIT Kerberos 5 Key Distribution Center ldap_principal2.c null pointer dereference$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2018-5710
01/16/20187.47.4MIT Kerberos 5 dump.c integer overflow$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2018-5709
11/23/20178.58.4MIT Kerberos 5 X.509 Data pkinit_crypto_openssl.c X509_NAME_oneline_ex memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2017-15088
09/13/20179.69.4MIT Kerberos 5 double free$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2017-11462
08/09/20176.56.3MIT Kerberos 5 KDC Assertion input validation$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2017-11368
07/20/20166.56.3MIT Kerberos 5 KDC Service validate_as_request null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2016-3120
03/26/20165.34.9MIT Kerberos kadmin ldap_principal2.c process_db_args null pointer dereference$0-$5k$0-$5kUnprovenOfficial Fix0.04CVE-2016-3119
02/03/20164.84.4MIT Kerberos xdr_nullstring memory corruption$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2015-8629
02/03/20167.57.0MIT Kerberos kadmin kadm5_modify_principal null pointer dereference$5k-$25k$0-$5kUnprovenOfficial Fix0.05CVE-2015-8630
02/03/20166.56.1MIT Kerberos rb5_unparse_name memory corruption$5k-$25k$0-$5kUnprovenOfficial Fix0.04CVE-2015-8631
11/13/20156.36.0MIT Kerberos iakerb.c gss_export_sec_context memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2015-2698
10/26/20154.34.1MIT Kerberos TGS Request bld_princ.c memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.06CVE-2015-2697

117 more entries are not shown

more entries by Mit

Interested in the pricing of exploits?

See the underground prices here!