{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25332 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25332 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25332 is a medium-severity vulnerability in Texas Instruments OMAP, published on 19 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-25332 and fix it if it is affected.\n\nWhat it is: CVE-2022-25332 is a medium-severity vulnerability in Texas Instruments OMAP, published on 19 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-25332 in the wild and no public exploit code.\n\nAffected product: Texas Instruments OMAP. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-25332/ (Markdown: https://insights.sbomify.com/CVE-2022-25332/index.md)","id":"CVE-2022-25332","markdown":"https://insights.sbomify.com/CVE-2022-25332/index.md","name":"CVE-2022-25332","record":{"aliases":["GHSA-3jg7-ghg4-5pxr"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TI OMAP L138","requires_auth":"high_privilege","summary":"An attacker with non-secure supervisor privileges can recover the Customer Encryption Key via a timing side channel in the AES module.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC-NL","cpe":[{"product":"omap_l138_firmware","vendor":"ti"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N/E:F/RL:U/RC:C/CR:H/IR:H/AR:H/MAV:L/MAC:L/MPR:H/MUI:N/MS:U/MC:H/MI:N/MA:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"},{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"The AES implementation in the Texas Instruments OMAP L138 (secure variants), present in mask ROM, suffers from a timing side channel which can be exploited by an adversary with non-secure supervisor privileges by managing cache contents and collecting timing information for different ciphertext inputs. Using this side channel, the SK_LOAD secure kernel routine can be used to recover the Customer Encryption Key (CEK).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SK_LOAD timing side channel during AES module decryption in Texas Instruments OMAP L138","id":"CVE-2022-25332","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Flawed SK_LOAD module authenticity check in Texas Instruments OMAP L138","id":"CVE-2022-25333"},"packages":[],"prev":{"headline":"Denial of service in Trend Micro ServerProtect for EMC Celerra","id":"CVE-2022-25331"},"products":["OMAP"],"published":"2023-10-19","related":[{"cvss_score":8.2,"headline":"Flawed SK_LOAD module authenticity check in Texas Instruments OMAP L138","id":"CVE-2022-25333","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":8.2,"headline":"Stack overflow on SK_LOAD signature length field in Texas Instruments OMAP L138","id":"CVE-2022-25334","kev_date_added":null,"published":"2023-10-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-27","vendors":["Texas Instruments"]},"summary":"An attacker with non-secure supervisor privileges can recover the Customer Encryption Key via a timing side channel in the AES module.","url":"https://insights.sbomify.com/CVE-2022-25332/"}