gsd-2021-28706
Vulnerability from gsd
Modified
2023-12-13 01:23
Details
guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of memory, it may be able to issue hypercalls to increase its memory allocation beyond the administrator established limit. This is a result of a calculation done with 32-bit precision, which may overflow. It would then only be the overflowed (and hence small) number which gets compared against the established upper bound.
Aliases
Aliases
{ GSD: { alias: "CVE-2021-28706", description: "guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of memory, it may be able to issue hypercalls to increase its memory allocation beyond the administrator established limit. This is a result of a calculation done with 32-bit precision, which may overflow. It would then only be the overflowed (and hence small) number which gets compared against the established upper bound.", id: "GSD-2021-28706", references: [ "https://www.suse.com/security/cve/CVE-2021-28706.html", "https://www.debian.org/security/2021/dsa-5017", "https://linux.oracle.com/cve/CVE-2021-28706.html", ], }, gsd: { metadata: { exploitCode: "unknown", remediation: "unknown", reportConfidence: "confirmed", type: "vulnerability", }, osvSchema: { aliases: [ "CVE-2021-28706", ], details: "guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of memory, it may be able to issue hypercalls to increase its memory allocation beyond the administrator established limit. This is a result of a calculation done with 32-bit precision, which may overflow. It would then only be the overflowed (and hence small) number which gets compared against the established upper bound.", id: "GSD-2021-28706", modified: "2023-12-13T01:23:29.040189Z", schema_version: "1.4.0", }, }, namespaces: { "cve.org": { CVE_data_meta: { ASSIGNER: "security@xen.org", ID: "CVE-2021-28706", STATE: "PUBLIC", }, affects: { vendor: { vendor_data: [ { product: { product_data: [ { product_name: "xen", version: { version_data: [ { version_value: "4.12.x", }, ], }, }, { product_name: "xen", version: { version_data: [ { version_affected: "?<", version_value: "4.12", }, { version_affected: ">=", version_value: "4.14.x", }, { version_affected: "!>", version_value: "4.15.x", }, ], }, }, { product_name: "xen", version: { version_data: [ { version_value: "xen-unstable", }, ], }, }, { product_name: "xen", version: { version_data: [ { version_value: "4.13.x", }, ], }, }, ], }, vendor_name: "Xen", }, ], }, }, configuration: { configuration_data: { description: { description_data: [ { lang: "eng", value: "All Xen versions from at least 3.2 onwards are affected.\n\nOn x86, only Xen builds with the BIGMEM configuration option enabled are\naffected. (This option is off by default.)\n\nOnly hosts with more than 16 TiB of memory are affected.", }, ], }, }, }, credit: { credit_data: { description: { description_data: [ { lang: "eng", value: "This issue was discovered by Julien Grall of Amazon.", }, ], }, }, }, data_format: "MITRE", data_type: "CVE", data_version: "4.0", description: { description_data: [ { lang: "eng", value: "guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of memory, it may be able to issue hypercalls to increase its memory allocation beyond the administrator established limit. This is a result of a calculation done with 32-bit precision, which may overflow. It would then only be the overflowed (and hence small) number which gets compared against the established upper bound.", }, ], }, impact: { impact_data: { description: { description_data: [ { lang: "eng", value: "A guest may be able too allocate unbounded amounts of memory to itself.\nThis may result in a Denial of Service (DoS) affecting the entire host.", }, ], }, }, }, problemtype: { problemtype_data: [ { description: [ { lang: "eng", value: "unknown", }, ], }, ], }, references: { reference_data: [ { name: "https://xenbits.xenproject.org/xsa/advisory-385.txt", refsource: "MISC", url: "https://xenbits.xenproject.org/xsa/advisory-385.txt", }, { name: "FEDORA-2021-03645e9807", refsource: "FEDORA", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/I7ZGWVVRI4XY2XSTBI3XEMWBXPDVX6OT/", }, { name: "DSA-5017", refsource: "DEBIAN", url: "https://www.debian.org/security/2021/dsa-5017", }, { name: "FEDORA-2021-2b3a2de94f", refsource: "FEDORA", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PXUI4VMD52CH3T7YXAG3J2JW7ZNN3SXF/", }, { name: "GLSA-202402-07", refsource: "GENTOO", url: "https://security.gentoo.org/glsa/202402-07", }, ], }, workaround: { workaround_data: { description: { description_data: [ { lang: "eng", value: "Setting the maximum amount of memory a guest may allocate to strictly\nless than 1023 GiB will avoid the vulnerability.", }, ], }, }, }, }, "nvd.nist.gov": { cve: { configurations: [ { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:o:xen:xen:*:*:*:*:*:*:*:*", matchCriteriaId: "1C6CF6CF-FA02-40B4-A285-167C1F8CE5C4", versionEndExcluding: "4.12", versionStartIncluding: "3.2", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:o:fedoraproject:fedora:34:*:*:*:*:*:*:*", matchCriteriaId: "A930E247-0B43-43CB-98FF-6CE7B8189835", vulnerable: true, }, { criteria: "cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*", matchCriteriaId: "80E516C0-98A4-4ADE-B69F-66A772E2BAAA", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*", matchCriteriaId: "FA6FEEC2-9F11-4643-8827-749718254FED", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, ], descriptions: [ { lang: "en", value: "guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of memory, it may be able to issue hypercalls to increase its memory allocation beyond the administrator established limit. This is a result of a calculation done with 32-bit precision, which may overflow. It would then only be the overflowed (and hence small) number which gets compared against the established upper bound.", }, { lang: "es", value: "Los huéspedes pueden exceder su límite de memoria designado Cuando a un huésped se le permite tener cerca de 16TiB de memoria, puede ser capaz de emitir hypercalls para aumentar su asignación de memoria más allá del límite establecido por el administrador. Esto es el resultado de un cálculo realizado con precisión de 32 bits, que puede desbordarse. En ese caso, sólo el número desbordado (y por tanto pequeño) se comparará con el límite superior establecido", }, ], id: "CVE-2021-28706", lastModified: "2024-02-04T08:15:08.880", metrics: { cvssMetricV2: [ { acInsufInfo: false, baseSeverity: "HIGH", cvssData: { accessComplexity: "LOW", accessVector: "NETWORK", authentication: "NONE", availabilityImpact: "COMPLETE", baseScore: 7.8, confidentialityImpact: "NONE", integrityImpact: "NONE", vectorString: "AV:N/AC:L/Au:N/C:N/I:N/A:C", version: "2.0", }, exploitabilityScore: 10, impactScore: 6.9, obtainAllPrivilege: false, obtainOtherPrivilege: false, obtainUserPrivilege: false, source: "nvd@nist.gov", type: "Primary", userInteractionRequired: false, }, ], cvssMetricV31: [ { cvssData: { attackComplexity: "LOW", attackVector: "NETWORK", availabilityImpact: "HIGH", baseScore: 8.6, baseSeverity: "HIGH", confidentialityImpact: "NONE", integrityImpact: "NONE", privilegesRequired: "NONE", scope: "CHANGED", userInteraction: "NONE", vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H", version: "3.1", }, exploitabilityScore: 3.9, impactScore: 4, source: "nvd@nist.gov", type: "Primary", }, ], }, published: "2021-11-24T01:15:08.127", references: [ { source: "security@xen.org", url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/I7ZGWVVRI4XY2XSTBI3XEMWBXPDVX6OT/", }, { source: "security@xen.org", url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PXUI4VMD52CH3T7YXAG3J2JW7ZNN3SXF/", }, { source: "security@xen.org", url: "https://security.gentoo.org/glsa/202402-07", }, { source: "security@xen.org", tags: [ "Third Party Advisory", ], url: "https://www.debian.org/security/2021/dsa-5017", }, { source: "security@xen.org", tags: [ "Mitigation", "Patch", "Third Party Advisory", ], url: "https://xenbits.xenproject.org/xsa/advisory-385.txt", }, ], sourceIdentifier: "security@xen.org", vulnStatus: "Modified", weaknesses: [ { description: [ { lang: "en", value: "CWE-770", }, ], source: "nvd@nist.gov", type: "Primary", }, ], }, }, }, }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.