OESA-2023-1264 (CVE-2023-30630)
Vulnerability from osv_openeuler – Published: 2023-04-28 11:05 – Updated: 2026-08-06 11:05 – Source websiteDmidecode reports information about your system's hardware as described in your system BIOS according to the SMBIOS/DMI standard (see a sample output). This information typically includes system manufacturer, model name, serial number, BIOS version, asset tag as well as a lot of other details of varying level of interest and reliability depending on the manufacturer. This will often include usage status for the CPU sockets, expansion slots (e.g. AGP, PCI, ISA) and memory module slots, and the list of I/O ports (e.g. serial, parallel, USB).DMI data can be used to enable or disable specific portions of kernel code depending on the specific hardware. Thus, one use of dmidecode is for kernel developers to detect system "signatures" and add them to the kernel source code when needed.
Security Fix(es):
Dmidecode before 3.5 allows -dump-bin to overwrite a local file. This has security relevance because, for example, execution of Dmidecode via Sudo is plausible.(CVE-2023-30630)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"dmidecode-3.2-4.oe1.aarch64.rpm",
"dmidecode-debugsource-3.2-4.oe1.aarch64.rpm",
"dmidecode-debuginfo-3.2-4.oe1.aarch64.rpm"
],
"src": [
"dmidecode-3.2-4.oe1.src.rpm"
],
"x86_64": [
"dmidecode-debuginfo-3.2-4.oe1.x86_64.rpm",
"dmidecode-debugsource-3.2-4.oe1.x86_64.rpm",
"dmidecode-3.2-4.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP1",
"name": "dmidecode",
"purl": "pkg:rpm/openEuler/dmidecode\u0026distro=openEuler-20.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.2-4.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"dmidecode-debuginfo-3.2-4.oe1.aarch64.rpm",
"dmidecode-debugsource-3.2-4.oe1.aarch64.rpm",
"dmidecode-3.2-4.oe1.aarch64.rpm"
],
"src": [
"dmidecode-3.2-4.oe1.src.rpm"
],
"x86_64": [
"dmidecode-3.2-4.oe1.x86_64.rpm",
"dmidecode-debuginfo-3.2-4.oe1.x86_64.rpm",
"dmidecode-debugsource-3.2-4.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP3",
"name": "dmidecode",
"purl": "pkg:rpm/openEuler/dmidecode\u0026distro=openEuler-20.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.2-4.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"dmidecode-3.3-6.oe2203.aarch64.rpm",
"dmidecode-debugsource-3.3-6.oe2203.aarch64.rpm",
"dmidecode-debuginfo-3.3-6.oe2203.aarch64.rpm",
"dmidecode-debugsource-3.4-3.oe2203sp1.aarch64.rpm",
"dmidecode-3.4-3.oe2203sp1.aarch64.rpm",
"dmidecode-debuginfo-3.4-3.oe2203sp1.aarch64.rpm"
],
"src": [
"dmidecode-3.3-6.oe2203.src.rpm",
"dmidecode-3.4-3.oe2203sp1.src.rpm"
],
"x86_64": [
"dmidecode-3.3-6.oe2203.x86_64.rpm",
"dmidecode-debugsource-3.3-6.oe2203.x86_64.rpm",
"dmidecode-debuginfo-3.3-6.oe2203.x86_64.rpm",
"dmidecode-debuginfo-3.4-3.oe2203sp1.x86_64.rpm",
"dmidecode-debugsource-3.4-3.oe2203sp1.x86_64.rpm",
"dmidecode-3.4-3.oe2203sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS",
"name": "dmidecode",
"purl": "pkg:rpm/openEuler/dmidecode\u0026distro=openEuler-22.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.4-3.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"dmidecode-debugsource-3.4-3.oe2203sp1.aarch64.rpm",
"dmidecode-3.4-3.oe2203sp1.aarch64.rpm",
"dmidecode-debuginfo-3.4-3.oe2203sp1.aarch64.rpm"
],
"src": [
"dmidecode-3.4-3.oe2203sp1.src.rpm"
],
"x86_64": [
"dmidecode-debuginfo-3.4-3.oe2203sp1.x86_64.rpm",
"dmidecode-debugsource-3.4-3.oe2203sp1.x86_64.rpm",
"dmidecode-3.4-3.oe2203sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP1",
"name": "dmidecode",
"purl": "pkg:rpm/openEuler/dmidecode\u0026distro=openEuler-22.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.4-3.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "Dmidecode reports information about your system\u0027s hardware as described in your system BIOS according to the SMBIOS/DMI standard (see a sample output). This information typically includes system manufacturer, model name, serial number, BIOS version, asset tag as well as a lot of other details of varying level of interest and reliability depending on the manufacturer. This will often include usage status for the CPU sockets, expansion slots (e.g. AGP, PCI, ISA) and memory module slots, and the list of I/O ports (e.g. serial, parallel, USB).DMI data can be used to enable or disable specific portions of kernel code depending on the specific hardware. Thus, one use of dmidecode is for kernel developers to detect system \"signatures\" and add them to the kernel source code when needed.\r\n\r\nSecurity Fix(es):\r\n\r\nDmidecode before 3.5 allows -dump-bin to overwrite a local file. This has security relevance because, for example, execution of Dmidecode via Sudo is plausible.(CVE-2023-30630)",
"id": "OESA-2023-1264",
"modified": "2026-08-06T11:05:44Z",
"published": "2023-04-28T11:05:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1264"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-30630"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "dmidecode security update",
"upstream": [
"CVE-2023-30630"
]
}
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.
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.