DescriptionAn issue was discovered in Xen through 4.11.x. The logic in oxenstored for handling writes depended on the order of evaluation of expressions making up a tuple. As indicated in section 7.7.3 "Operations on data structures" of the OCaml manual, the order of evaluation of subexpressions is not specified. In practice, different implementations behave differently. Thus, oxenstored may not enforce the configured quota-maxentity. This allows a malicious or buggy guest to write as many xenstore entries as it wishes, causing unbounded memory usage in oxenstored. This can lead to a system-wide DoS.
Overall state of this security issue: Running
This issue is currently rated as having moderate severity.SUSE Bugzilla entry: 1103279 [RESOLVED / INVALID] No SUSE Security Announcements cross referenced.
List of packages in QA
|SUSE CaaS Platform 3.0||
|SUSE CaaS Platform ALL||
|SUSE Linux Enterprise Desktop 12 SP3||
|SUSE Linux Enterprise Server 12 SP3||
|SUSE Linux Enterprise Server for SAP Applications 12 SP3||
|SUSE Linux Enterprise Software Development Kit 12 SP3||
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification.
|CaaS Platform 2.0||xen||In progress|
|CaaS Platform 3.0||xen||In progress|
|SUSE Linux Enterprise Desktop 12 SP3||xen||In progress|
|SUSE Linux Enterprise Module for Basesystem 15 GA||xen||Not affected|
|SUSE Linux Enterprise Module for Server Applications 15 GA||xen||Not affected|
|SUSE Linux Enterprise SDK 11 SP4||xen||Not affected|
|SUSE Linux Enterprise SDK 12 SP3||xen||In progress|
|SUSE Linux Enterprise Server 11 SP4||xen||Not affected|
|SUSE Linux Enterprise Server 12 SP3||xen||In progress|