OESA-2021-1024 (CVE-2020-29361)
Vulnerability from osv_openeuler – Published: 2021-02-05 11:04 – Updated: 2026-08-06 11:04 – Source websiteProvides a way to load and enumerate PKCS#11 modules. Provides a standard configuration setup for installing PKCS#11 modules in such a way that they're discoverable. Also solves problems with coordinating the use of PKCS#11 by different components or libraries living in the same process.\r\n\r\n Security Fix(es):\r\n\r\n An issue was discovered in p11-kit 0.21.1 through 0.23.21. Multiple integer overflows have been discovered in the array allocations in the p11-kit library and the p11-kit list command, where overflow checks are missing before calling realloc or calloc.(CVE-2020-29361)\r\n\r\n An issue was discovered in p11-kit 0.21.1 through 0.23.21. A heap-based buffer over-read has been discovered in the RPC protocol used by thep11-kit server/remote commands and the client library. When the remote entity supplies a byte array through a serialized PKCS#11 function call, the receiving entity may allow the reading of up to 4 bytes of memory past the heap allocation.(CVE-2020-29362)\r\n\r\n An issue was discovered in p11-kit 0.23.6 through 0.23.21. A heap-based buffer overflow has been discovered in the RPC protocol used by p11-kit server/remote commands and the client library. When the remote entity supplies a serialized byte array in a CK_ATTRIBUTE, the receiving entity may not allocate sufficient length for the buffer to store the deserialized value.(CVE-2020-29363)\r\n\r\n
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"p11-kit-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-debuginfo-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-debugsource-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-devel-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-help-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-trust-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-debuginfo-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-debugsource-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-devel-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-help-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-trust-0.23.20-2.oe1.aarch64.rpm"
],
"src": [
"p11-kit-0.23.20-2.oe1.src.rpm",
"p11-kit-0.23.20-2.oe1.src.rpm"
],
"x86_64": [
"p11-kit-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-debuginfo-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-debugsource-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-devel-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-help-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-trust-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-debuginfo-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-debugsource-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-devel-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-help-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-trust-0.23.20-2.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS",
"name": "p11-kit",
"purl": "pkg:rpm/openEuler/p11-kit\u0026distro=openEuler-20.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.23.20-2.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"p11-kit-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-debuginfo-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-debugsource-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-devel-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-help-0.23.20-2.oe1.aarch64.rpm",
"p11-kit-trust-0.23.20-2.oe1.aarch64.rpm"
],
"src": [
"p11-kit-0.23.20-2.oe1.src.rpm"
],
"x86_64": [
"p11-kit-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-debuginfo-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-debugsource-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-devel-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-help-0.23.20-2.oe1.x86_64.rpm",
"p11-kit-trust-0.23.20-2.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP1",
"name": "p11-kit",
"purl": "pkg:rpm/openEuler/p11-kit\u0026distro=openEuler-20.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.23.20-2.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "Provides a way to load and enumerate PKCS#11 modules. Provides a standard configuration setup for installing PKCS#11 modules in such a way that they\u0027re discoverable. Also solves problems with coordinating the use of PKCS#11 by different components or libraries living in the same process.\\r\\n\\r\\n\r\nSecurity Fix(es):\\r\\n\\r\\n\r\nAn issue was discovered in p11-kit 0.21.1 through 0.23.21. Multiple integer overflows have been discovered in the array allocations in the p11-kit library and the p11-kit list command, where overflow checks are missing before calling realloc or calloc.(CVE-2020-29361)\\r\\n\\r\\n\nAn issue was discovered in p11-kit 0.21.1 through 0.23.21. A heap-based buffer over-read has been discovered in the RPC protocol used by thep11-kit server/remote commands and the client library. When the remote entity supplies a byte array through a serialized PKCS#11 function call, the receiving entity may allow the reading of up to 4 bytes of memory past the heap allocation.(CVE-2020-29362)\\r\\n\\r\\n\nAn issue was discovered in p11-kit 0.23.6 through 0.23.21. A heap-based buffer overflow has been discovered in the RPC protocol used by p11-kit server/remote commands and the client library. When the remote entity supplies a serialized byte array in a CK_ATTRIBUTE, the receiving entity may not allocate sufficient length for the buffer to store the deserialized value.(CVE-2020-29363)\\r\\n\\r\\n",
"id": "OESA-2021-1024",
"modified": "2026-08-06T11:04:15Z",
"published": "2021-02-05T11:04:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1024"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-29361"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-29362"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-29363"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "p11-kit security update",
"upstream": [
"CVE-2020-29361",
"CVE-2020-29362",
"CVE-2020-29363"
]
}
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.