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: 04 July 2026 12:14 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 · 13 mapping(s) from 5 framework(s): ATT&CK 6 (mostly) · CAPEC 4 (partial) · STIG oracle linux 8 1 (mostly) · STIG oracle linux 9 1 (mostly) · STIG rhel 7 1 (mostly)
NIST 800-53 r5 controls that address this weakness (1)AI
| 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. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-31813 | 7.0 | 9.8 | 0.0314 | 2022-06-09 |
CVE-2024-45410 | 7.0 | 9.8 | 0.0151 | 2024-09-19 |
CVE-2025-48865 UPD | 7.0 | 9.1 | 0.0051 | 2025-05-30 |
CVE-2025-59951 | 7.0 | 9.1 | 0.0465 | 2025-10-01 |
CVE-2026-44183 UPD | 7.0 | 9.8 | 0.0022 | 2026-05-12 |
CVE-2026-48772 | 7.0 | 10.0 | 0.0019 | 2026-06-19 |
CVE-2026-12249 | 7.0 | 9.0 | 0.0011 | 2026-06-22 |
CVE-2021-21373 | 5.5 | 7.5 | 0.0115 | 2021-03-26 |
CVE-2021-21374 | 5.5 | 8.1 | 0.0103 | 2021-03-26 |
CVE-2022-2255 | 5.5 | 7.5 | 0.0069 | 2022-08-25 |
CVE-2024-27773 UPD | 5.5 | 8.8 | 0.0036 | 2024-03-18 |
CVE-2024-23105 | 5.5 | 7.5 | 0.0044 | 2024-05-14 |
CVE-2024-47880 | 5.5 | 8.1 | 0.0036 | 2024-10-24 |
CVE-2025-27913 | 5.5 | 7.5 | 0.0017 | 2025-03-10 |
CVE-2025-47424 UPD | 5.5 | 7.1 | 0.0013 | 2025-05-09 |
CVE-2025-55292 | 5.5 | 8.2 | 0.0013 | 2026-01-28 |
CVE-2025-69240 | 5.5 | 8.8 | 0.0015 | 2026-03-16 |
CVE-2026-35391 | 5.5 | 7.5 | 0.0014 | 2026-04-06 |
CVE-2026-43634 UPD | 5.5 | 7.5 | 0.0024 | 2026-05-19 |
CVE-2022-4537 | 3.5 | 6.5 | 0.0032 | 2023-05-09 |
CVE-2024-0789 | 3.5 | 5.3 | 0.0025 | 2024-06-19 |
CVE-2024-6171 | 3.5 | 5.3 | 0.0025 | 2024-07-09 |
CVE-2022-4532 | 3.5 | 6.5 | 0.0021 | 2024-08-17 |
CVE-2022-4536 | 3.5 | 5.3 | 0.0024 | 2024-08-31 |
CVE-2022-4539 | 3.5 | 5.3 | 0.0063 | 2024-08-31 |