ALSA-2022:6443 (CVE-2021-46659)
Vulnerability from osv_almalinux – Published: 2022-09-13 00:00 – Updated: 2022-10-14 07:41 – Source websiteMariaDB is a multi-user, multi-threaded SQL database server that is binary compatible with MySQL.
The following packages have been upgraded to a later upstream version: mariadb (10.3.35), galera (25.3.35).
Security Fix(es):
- mariadb: MariaDB through 10.5.9 allows attackers to trigger a convert_const_to_int use-after-free when the BIGINT data type is used (CVE-2021-46669)
- mysql: Server: FTS unspecified vulnerability (CPU Apr 2022) (CVE-2022-21427)
- mariadb: lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer (CVE-2022-24048)
- mariadb: lack of validating the existence of an object prior to performing operations on the object (CVE-2022-24050)
- mariadb: lack of proper validation of a user-supplied string before using it as a format specifier (CVE-2022-24051)
- mariadb: CONNECT storage engine heap-based buffer overflow (CVE-2022-24052)
- mariadb: assertion failure in Item_args::walk_arg (CVE-2022-27376)
- mariadb: use-after-poison when complex conversion is involved in blob (CVE-2022-27377)
- mariadb: server crash in create_tmp_table::finalize (CVE-2022-27378)
- mariadb: server crash in component arg_comparator::compare_real_fixed (CVE-2022-27379)
- mariadb: server crash at my_decimal::operator= (CVE-2022-27380)
- mariadb: server crash at Field::set_default via specially crafted SQL statements (CVE-2022-27381)
- mariadb: use-after-poison in my_strcasecmp_8bit() of ctype-simple.c (CVE-2022-27383)
- mariadb: crash via component Item_subselect::init_expr_cache_tracker (CVE-2022-27384)
- mariadb: server crashes in query_arena::set_query_arena upon SELECT from view (CVE-2022-27386)
- mariadb: assertion failures in decimal_bin_size (CVE-2022-27387)
- mariadb: assertion failure in compare_order_elements (CVE-2022-27445)
- mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27447)
- mariadb: crash in multi-update and implicit grouping (CVE-2022-27448)
- mariadb: assertion failure in sql/item_func.cc (CVE-2022-27449)
- mariadb: assertion failure in sql/item_cmpfunc.cc (CVE-2022-27452)
- mariadb: assertion failure in VDec::VDec at /sql/sql_type.cc (CVE-2022-27456)
- mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27458)
- mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31622)
- mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31623)
- mariadb: server crash at Item_subselect::init_expr_cache_tracker (CVE-2022-32083)
- mariadb: server crash in Item_func_in::cleanup/Item::cleanup_processor (CVE-2022-32085)
- mariadb: server crash in Item_args::walk_args (CVE-2022-32087)
- mariadb: segmentation fault in Exec_time_tracker::get_loops/Filesort_tracker::report_use/filesort (CVE-2022-32088)
- mariadb: Crash executing query with VIEW, aggregate and subquery (CVE-2021-46659)
- mariadb: MariaDB allows an application crash in find_field_in_tables and find_order_in_list via an unused common table expression (CTE) (CVE-2021-46661)
- mariadb: MariaDB through 10.5.13 allows a ha_maria::extra application crash via certain SELECT statements (CVE-2021-46663)
- mariadb: MariaDB through 10.5.9 allows an application crash in sub_select_postjoin_aggr for a NULL value of aggr (CVE-2021-46664)
- mariadb: MariaDB through 10.5.9 allows a sql_parse.cc application crash because of incorrect used_tables expectations (CVE-2021-46665)
- mariadb: MariaDB through 10.5.9 allows an application crash via certain long SELECT DISTINCT statements (CVE-2021-46668)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Bug Fix(es):
- [Tracker] Rebase to Galera 25.3.35 for MariaDB-10.3 (BZ#2107075)
{
"affected": [
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "Judy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.5-18.module_el8.6.0+3139+3c630e87"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "Judy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.5-18.module_el8.6.0+3072+3c630e87"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "galera"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "25.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-backup"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-common"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-devel"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-embedded"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-embedded-devel"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-errmsg"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-gssapi-server"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-oqgraph-engine"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-server"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-server-galera"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-server-utils"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:8",
"name": "mariadb-test"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3:10.3.35-1.module_el8.6.0+3265+230ed96b"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"details": "MariaDB is a multi-user, multi-threaded SQL database server that is binary compatible with MySQL. \n\nThe following packages have been upgraded to a later upstream version: mariadb (10.3.35), galera (25.3.35).\n\nSecurity Fix(es):\n\n* mariadb: MariaDB through 10.5.9 allows attackers to trigger a convert_const_to_int use-after-free when the BIGINT data type is used (CVE-2021-46669)\n* mysql: Server: FTS unspecified vulnerability (CPU Apr 2022) (CVE-2022-21427)\n* mariadb: lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer (CVE-2022-24048)\n* mariadb: lack of validating the existence of an object prior to performing operations on the object (CVE-2022-24050)\n* mariadb: lack of proper validation of a user-supplied string before using it as a format specifier (CVE-2022-24051)\n* mariadb: CONNECT storage engine heap-based buffer overflow (CVE-2022-24052)\n* mariadb: assertion failure in Item_args::walk_arg (CVE-2022-27376)\n* mariadb: use-after-poison when complex conversion is involved in blob (CVE-2022-27377)\n* mariadb: server crash in create_tmp_table::finalize (CVE-2022-27378)\n* mariadb: server crash in component arg_comparator::compare_real_fixed (CVE-2022-27379)\n* mariadb: server crash at my_decimal::operator= (CVE-2022-27380)\n* mariadb: server crash at Field::set_default via specially crafted SQL statements (CVE-2022-27381)\n* mariadb: use-after-poison in my_strcasecmp_8bit() of ctype-simple.c (CVE-2022-27383)\n* mariadb: crash via component Item_subselect::init_expr_cache_tracker (CVE-2022-27384)\n* mariadb: server crashes in query_arena::set_query_arena upon SELECT from view (CVE-2022-27386)\n* mariadb: assertion failures in decimal_bin_size (CVE-2022-27387)\n* mariadb: assertion failure in compare_order_elements (CVE-2022-27445)\n* mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27447)\n* mariadb: crash in multi-update and implicit grouping (CVE-2022-27448)\n* mariadb: assertion failure in sql/item_func.cc (CVE-2022-27449)\n* mariadb: assertion failure in sql/item_cmpfunc.cc (CVE-2022-27452)\n* mariadb: assertion failure in VDec::VDec at /sql/sql_type.cc (CVE-2022-27456)\n* mariadb: use-after-poison in Binary_string::free_buffer (CVE-2022-27458)\n* mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31622)\n* mariadb: improper locking due to the unreleased lock in extra/mariabackup/ds_compress.cc (CVE-2022-31623)\n* mariadb: server crash at Item_subselect::init_expr_cache_tracker (CVE-2022-32083)\n* mariadb: server crash in Item_func_in::cleanup/Item::cleanup_processor (CVE-2022-32085)\n* mariadb: server crash in Item_args::walk_args (CVE-2022-32087)\n* mariadb: segmentation fault in Exec_time_tracker::get_loops/Filesort_tracker::report_use/filesort (CVE-2022-32088)\n* mariadb: Crash executing query with VIEW, aggregate and subquery (CVE-2021-46659)\n* mariadb: MariaDB allows an application crash in find_field_in_tables and find_order_in_list via an unused common table expression (CTE) (CVE-2021-46661)\n* mariadb: MariaDB through 10.5.13 allows a ha_maria::extra application crash via certain SELECT statements (CVE-2021-46663)\n* mariadb: MariaDB through 10.5.9 allows an application crash in sub_select_postjoin_aggr for a NULL value of aggr (CVE-2021-46664)\n* mariadb: MariaDB through 10.5.9 allows a sql_parse.cc application crash because of incorrect used_tables expectations (CVE-2021-46665)\n* mariadb: MariaDB through 10.5.9 allows an application crash via certain long SELECT DISTINCT statements (CVE-2021-46668)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n\nBug Fix(es):\n\n* [Tracker] Rebase to Galera 25.3.35 for MariaDB-10.3 (BZ#2107075)",
"id": "ALSA-2022:6443",
"modified": "2022-10-14T07:41:44Z",
"published": "2022-09-13T00:00:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2022:6443"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2021-46659"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2021-46661"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2021-46663"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2021-46664"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2021-46665"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2021-46668"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2021-46669"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-21427"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-24048"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-24050"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-24051"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-24052"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27376"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27377"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27378"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27379"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27380"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27381"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27383"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27384"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27386"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27387"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27445"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27447"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27448"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27449"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27452"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27456"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-27458"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-31622"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-31623"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-32083"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-32085"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-32087"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2022-32088"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2049302"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2050017"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2050022"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2050024"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2050026"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2050032"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2050034"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2068211"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2068233"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2068234"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2069833"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2074817"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2074947"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2074949"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2074951"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2074966"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2074981"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2074996"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2074999"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2075005"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2075006"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2075691"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2075693"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2075694"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2075695"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2075697"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2075700"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2076145"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2082644"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2092354"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2092360"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2104425"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2104431"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2104434"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2106008"
},
{
"type": "ADVISORY",
"url": "https://errata.almalinux.org/8/ALSA-2022-6443.html"
}
],
"related": [
"CVE-2021-46659",
"CVE-2021-46661",
"CVE-2021-46663",
"CVE-2021-46664",
"CVE-2021-46665",
"CVE-2021-46668",
"CVE-2021-46669",
"CVE-2022-21427",
"CVE-2022-24048",
"CVE-2022-24050",
"CVE-2022-24051",
"CVE-2022-24052",
"CVE-2022-27376",
"CVE-2022-27377",
"CVE-2022-27378",
"CVE-2022-27379",
"CVE-2022-27380",
"CVE-2022-27381",
"CVE-2022-27383",
"CVE-2022-27384",
"CVE-2022-27386",
"CVE-2022-27387",
"CVE-2022-27445",
"CVE-2022-27447",
"CVE-2022-27448",
"CVE-2022-27449",
"CVE-2022-27452",
"CVE-2022-27456",
"CVE-2022-27458",
"CVE-2022-31622",
"CVE-2022-31623",
"CVE-2022-32083",
"CVE-2022-32085",
"CVE-2022-32087",
"CVE-2022-32088"
],
"schema_version": "1.7.0",
"summary": "Moderate: mariadb:10.3 security and bug fix update",
"upstream": [
"CVE-2021-46659",
"CVE-2021-46661",
"CVE-2021-46663",
"CVE-2021-46664",
"CVE-2021-46665",
"CVE-2021-46668",
"CVE-2021-46669",
"CVE-2022-21427",
"CVE-2022-24048",
"CVE-2022-24050",
"CVE-2022-24051",
"CVE-2022-24052",
"CVE-2022-27376",
"CVE-2022-27377",
"CVE-2022-27378",
"CVE-2022-27379",
"CVE-2022-27380",
"CVE-2022-27381",
"CVE-2022-27383",
"CVE-2022-27384",
"CVE-2022-27386",
"CVE-2022-27387",
"CVE-2022-27445",
"CVE-2022-27447",
"CVE-2022-27448",
"CVE-2022-27449",
"CVE-2022-27452",
"CVE-2022-27456",
"CVE-2022-27458",
"CVE-2022-31622",
"CVE-2022-31623",
"CVE-2022-32083",
"CVE-2022-32085",
"CVE-2022-32087",
"CVE-2022-32088"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.