{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-33982 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-33982 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-33982 is a medium-severity vulnerability in n/a, published on 24 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-33982 and fix it if it is affected.\n\nWhat it is: CVE-2023-33982 is a medium-severity vulnerability in n/a, published on 24 May 2023. 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-2023-33982 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-2023-33982/ (Markdown: https://insights.sbomify.com/CVE-2023-33982/index.md)","id":"CVE-2023-33982","markdown":"https://insights.sbomify.com/CVE-2023-33982/index.md","name":"CVE-2023-33982","record":{"aliases":["GHSA-f7g9-f9cq-4whw"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Briar secure messenger","requires_auth":"none","summary":"Briar's handshake protocol lacks forward secrecy, allowing decryption of past traffic if both accounts are later compromised, though Tor encryption mitigates this risk.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"briar","vendor":"briarproject"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"Bramble Handshake Protocol (BHP) in Briar before 1.5.3 is not forward secure: eavesdroppers can decrypt network traffic between two accounts if they later compromise both accounts. NOTE: the eavesdropping is typically impractical because BHP runs over an encrypted session that uses the Tor hidden service protocol.","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":"Weak cryptography in n/a","id":"CVE-2023-33982","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2023-33983"},"packages":[],"prev":{"headline":"Business logic in n/a","id":"CVE-2023-33981"},"products":["n/a"],"published":"2023-05-24","related":[{"cvss_score":7.5,"headline":"Bramble Synchronisation Protocol (BSP) in Briar before 1.4.22 allows attackers to cause a denial of service (repeated application crashes) v","id":"CVE-2023-33980","kev_date_added":null,"published":"2023-05-24"},{"cvss_score":7.4,"headline":"Missing authorization in n/a","id":"CVE-2023-33983","kev_date_added":null,"published":"2023-05-24"},{"cvss_score":6.5,"headline":"Business logic in n/a","id":"CVE-2023-33981","kev_date_added":null,"published":"2023-05-24"}],"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":"2025-01-16","vendors":["n/a"]},"summary":"Briar's handshake protocol lacks forward secrecy, allowing decryption of past traffic if both accounts are later compromised, though Tor encryption mitigates this risk.","url":"https://insights.sbomify.com/CVE-2023-33982/"}