Security Resilience

CVE-2024-0161

Dell Poweredge T360 Firmware ≤ 1.1.1

Published
13 March 2024
Modified
04 February 2025
Patch / advisory
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:H
EPSS Score 0.0020 10th percentile
Risk Priority 47 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-0161 is a high-severity Improper Input Validation (CWE-20) vulnerability in Dell Poweredge T360 Firmware. Its CVSS base score is 7.2 (High).

Operationally, ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Dell PowerEdge Server BIOS and Dell Precision Rack BIOS contain an Improper SMM communication buffer verification vulnerability. A local low privileged attacker could potentially exploit this vulnerability leading to arbitrary writes to SMRAM.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-38303Same product: Dell Dss 8440
CVE-2023-32460Same product: Dell Dss 8440
CVE-2024-0173Same product: Dell Dss 8440
CVE-2024-0154Same product: Dell Dss 8440
CVE-2024-25942Same product: Dell Poweredge C4130
CVE-2023-25938Same vendor: Dell
CVE-2023-28054Same vendor: Dell
CVE-2023-28026Same vendor: Dell
CVE-2023-28033Same vendor: Dell
CVE-2023-28027Same vendor: Dell

Affected Assets

dell
poweredge t360 firmware
≤ 1.1.1
dell
poweredge r360 firmware
≤ 1.1.1
dell
poweredge r650 firmware
≤ 1.13.2
dell
poweredge r750 firmware
≤ 1.13.2
dell
poweredge r750xa firmware
≤ 1.13.2
dell
poweredge c6520 firmware
≤ 1.13.2
dell
poweredge mx750c firmware
≤ 1.13.2
dell
poweredge r550 firmware
≤ 1.13.2
dell
poweredge r450 firmware
≤ 1.13.2
dell
poweredge r650xs firmware
≤ 1.13.2
+76 more product configuration(s) — see NVD for full list

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing input validation through analysis or test cases.

SI-10 directly requires validity checks on information inputs, structurally preventing improper or missing validation.

Requiring documented development standards and tools can embed input-validation practices into the engineering process.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.25 mandates security requirements, secure coding guidelines, checkpoints, testing (incl. code scans) and developer training in the SDLC, which reaches a slice of input validation defects but leaves the majority (incomplete enforcement, second-order inputs, parser differentials, post-validation canonicalization) unaddressed as in the SA-3 and A.8.28 anchors.

blocks

Mandating input controls that include integrity checks and input validation ensures that untrusted data is examined before use, blocking the root cause of many injection and malformed-data weaknesses.

blocks

Security-by-design principles explicitly call for data validation and sanitization at every layer, reducing the chance that malformed or malicious input will be processed without scrutiny.

prevents

Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.

finds

Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-20, a class-level weakness, and none of its children carries one either.

References