CWE · MITRE source
CWE-348Use of Less Trusted Source
The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack.
Last updated: 16 October 2026 07:24 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 4 mapping(s) from 4 framework(s): STIG oracle linux 8 1 (mostly) · STIG oracle linux 9 1 (mostly) · STIG rhel 7 1 (mostly) · ATT&CK 1 (partial)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
DE.AE-03
- 7 hardening rules · 4 OS baselines
—
NIST 800-53 r5 controls PROPOSED for this weakness (1)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-21 | Secure Name/Address Resolution Service (Recursive or Caching Resolver) | SC | Prevents use of less-trusted or adversarial sources by requiring proof of origin and integrity before accepting responses. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-31813 UPD | 7.8 | 9.8 | 0.0354 | 2022-06-09 |
CVE-2024-45410 | 7.6 | 9.8 | 0.0151 | 2024-09-19 |
CVE-2025-59951 UPD | 7.4 | 9.1 | 0.0432 | 2025-10-01 |
CVE-2026-44183 UPD | 7.2 | 9.8 | 0.0033 | 2026-05-12 |
CVE-2026-48772 UPD | 7.1 | 10.0 | 0.0023 | 2026-06-19 |
CVE-2025-48865 UPD | 6.9 | 9.1 | 0.0045 | 2025-05-30 |
CVE-2026-61682 | 6.9 | 9.9 | 0.0038 | 2026-09-18 |
CVE-2026-58122 | 6.8 | 9.1 | 0.0037 | 2026-07-09 |
CVE-2026-90711 | 6.8 | 9.1 | 0.0033 | 2026-09-15 |
CVE-2026-92395 | 6.8 | 9.1 | 0.0033 | 2026-09-16 |
CVE-2026-16272 UPD | 6.6 | 9.1 | 0.0014 | 2026-09-09 |
CVE-2024-27773 UPD | 6.5 | 8.8 | 0.0036 | 2024-03-18 |
CVE-2025-69240 | 6.3 | 8.8 | 0.0015 | 2026-03-16 |
CVE-2026-55641 | 6.2 | 8.2 | 0.0032 | 2026-07-10 |
CVE-2021-21374 UPD | 6.1 | 8.1 | 0.0104 | 2021-03-26 |
CVE-2024-47880 | 6.1 | 8.1 | 0.0038 | 2024-10-24 |
CVE-2026-12249 | 6.1 | 9.0 | 0.0014 | 2026-06-22 |
CVE-2026-9561 UPD | 6.1 | 8.2 | 0.0028 | 2026-07-14 |
CVE-2026-46415 | 6.1 | 8.2 | 0.0023 | 2026-07-20 |
CVE-2022-2255 UPD | 6.0 | 7.5 | 0.0088 | 2022-08-25 |
CVE-2025-55292 UPD | 6.0 | 8.2 | 0.0015 | 2026-01-28 |
CVE-2026-43634 UPD | 5.8 | 7.5 | 0.0036 | 2026-05-19 |
CVE-2021-21373 UPD | 5.7 | 7.5 | 0.0115 | 2021-03-26 |
CVE-2024-23105 UPD | 5.7 | 7.5 | 0.0044 | 2024-05-14 |
CVE-2026-63770 UPD | 5.7 | 7.5 | 0.0029 | 2026-07-20 |