{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35755 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35755 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35755 is a high-severity vulnerability in n/a, published on 3 May 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-2020-35755 and fix it if it is affected.\n\nWhat it is: CVE-2020-35755 is a high-severity vulnerability in n/a, published on 3 May 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-2020-35755 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-2020-35755/ (Markdown: https://insights.sbomify.com/CVE-2020-35755/index.md)","id":"CVE-2020-35755","markdown":"https://insights.sbomify.com/CVE-2020-35755/index.md","name":"CVE-2020-35755","record":{"aliases":["GHSA-mq75-jhcv-prqv"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Libre Wireless router","requires_auth":"none","summary":"Attackers can read sensitive NVRAM data, including cleartext Wi-Fi passwords and service tokens, via the luci_service daemon on port 7777.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ls9_firmware","vendor":"librewireless"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"An issue was discovered on Libre Wireless LS9 LS1.5/p7040 devices. There is a luci_service Read_ NVRAM Direct Access Information Leak. The luci_service deamon running on port 7777 provides a sub-category of commands for which Read_ is prepended. Commands in this category are able to directly read the contents of the device configuration NVRAM. The NVRAM contains sensitive information, such as the Wi-Fi password (in cleartext), as well as connected account tokens for services such as Spotify.","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-2020-35755","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-35756"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2020-35754"},"products":["n/a"],"published":"2021-05-03","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-35757","kev_date_added":null,"published":"2021-05-03"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-35758","kev_date_added":null,"published":"2021-05-03"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-35756","kev_date_added":null,"published":"2021-05-03"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can read sensitive NVRAM data, including cleartext Wi-Fi passwords and service tokens, via the luci_service daemon on port 7777.","url":"https://insights.sbomify.com/CVE-2020-35755/"}