{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-47122 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-47122 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-47122 is a medium-severity vulnerability in goTenna Pro, published on 26 Sep 2024. 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-2024-47122 and fix it if it is affected.\n\nWhat it is: CVE-2024-47122 is a medium-severity vulnerability in goTenna Pro, published on 26 Sep 2024. 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-2024-47122 in the wild and no public exploit code.\n\nAffected product: goTenna Pro. 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-2024-47122/ (Markdown: https://insights.sbomify.com/CVE-2024-47122/index.md)","id":"CVE-2024-47122","markdown":"https://insights.sbomify.com/CVE-2024-47122/index.md","name":"CVE-2024-47122","record":{"aliases":["GHSA-j9vg-w22p-v5v2"],"analysis":{"component_type":"mobile_application","fix_type":"configuration_change","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"goTenna Pro App","requires_auth":"none","summary":"Attackers with physical access to the device can decrypt stored keys and broadcast communications due to insecure storage practices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"gotenna_pro","vendor":"gotenna"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"In the goTenna Pro App, the encryption keys are stored along with a \nstatic IV on the End User Device (EUD). This allows for complete \ndecryption of keys stored on the EUD if physically compromised. This \nallows an attacker to decrypt all encrypted broadcast communications \nbased on encryption keys stored on the EUD. This requires access to and \ncontrol of the EUD, so it is recommended to use strong access control \nmeasures and layered encryption on the EUD for more secure operation.","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":"Insecure Storage of Sensitive Information in goTenna Pro","id":"CVE-2024-47122","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Missing Support for Integrity Check in goTenna Pro","id":"CVE-2024-47123"},"packages":[],"prev":{"headline":"Weak Passwords Requirements in goTenna Pro","id":"CVE-2024-47121"},"products":["Pro"],"published":"2024-09-26","related":[{"cvss_score":8.7,"headline":"Missing Authentication for Critical Function in goTenna Pro","id":"CVE-2024-47130","kev_date_added":null,"published":"2024-09-26"},{"cvss_score":7.6,"headline":"Improper Restriction of Communication Channel to Intended Endpoints in goTenna Pro","id":"CVE-2024-47125","kev_date_added":null,"published":"2024-09-26"},{"cvss_score":7.1,"headline":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in goTenna Pro","id":"CVE-2024-47126","kev_date_added":null,"published":"2024-09-26"},{"cvss_score":6,"headline":"Weak Passwords Requirements in goTenna Pro","id":"CVE-2024-47121","kev_date_added":null,"published":"2024-09-26"},{"cvss_score":6,"headline":"Missing Support for Integrity Check in goTenna Pro","id":"CVE-2024-47123","kev_date_added":null,"published":"2024-09-26"},{"cvss_score":6,"headline":"Weak Authentication in goTenna Pro","id":"CVE-2024-47127","kev_date_added":null,"published":"2024-09-26"},{"cvss_score":5.3,"headline":"Insertion of Sensitive Information Into Sent Data in goTenna Pro","id":"CVE-2024-47128","kev_date_added":null,"published":"2024-09-26"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-10-17","vendors":["goTenna"]},"summary":"Attackers with physical access to the device can decrypt stored keys and broadcast communications due to insecure storage practices.","url":"https://insights.sbomify.com/CVE-2024-47122/"}