{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-38545 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-38545 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-38545 is a medium-severity vulnerability in n/a, published on 11 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-38545 and fix it if it is affected.\n\nWhat it is: CVE-2021-38545 is a medium-severity vulnerability in n/a, published on 11 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-38545 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2021-38545/ (Markdown: https://insights.sbomify.com/CVE-2021-38545/index.md)","id":"CVE-2021-38545","markdown":"https://insights.sbomify.com/CVE-2021-38545/index.md","name":"CVE-2021-38545","record":{"aliases":["GHSA-w4r6-6p34-f36w"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Raspberry Pi single-board computer","requires_auth":"none","summary":"Remote attackers can recover audio signals from Raspberry Pi speakers by analyzing power indicator LED fluctuations via optical sensors.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"raspberry_pi_3_model_b\\+_firmware","vendor":"raspberrypi"},{"product":"raspberry_pi_4_model_b_firmware","vendor":"raspberrypi"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Raspberry Pi 3 B+ and 4 B devices through 2021-08-09, in certain specific use cases in which the device supplies power to audio-output equipment, allow remote attackers to recover speech signals from an LED on the device, via a telescope and an electro-optical sensor, aka a \"Glowworm\" attack. We assume that the Raspberry Pi supplies power to some speakers. The power indicator LED of the Raspberry Pi is connected directly to the power line, as a result, the intensity of a device's power indicator LED is correlative to the power consumption. The sound played by the speakers affects the Raspberry Pi's power consumption and as a result is also correlative to the light intensity of the LED. By analyzing measurements obtained from an electro-optical sensor directed at the power indicator LED of the Raspberry Pi, we can recover the sound played by the speakers.","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":"Information disclosure in n/a","id":"CVE-2021-38545","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2021-38546"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2021-38544"},"products":["n/a"],"published":"2021-08-11","related":[{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-18068","kev_date_added":null,"published":"2019-04-04"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Remote attackers can recover audio signals from Raspberry Pi speakers by analyzing power indicator LED fluctuations via optical sensors.","url":"https://insights.sbomify.com/CVE-2021-38545/"}