{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-46633 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-46633 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46633 is a high-severity vulnerability in n/a, published on 1 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46633 and fix it if it is affected.\n\nWhat it is: CVE-2025-46633 is a high-severity vulnerability in n/a, published on 1 May 2025. 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-2025-46633 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-2025-46633/ (Markdown: https://insights.sbomify.com/CVE-2025-46633/index.md)","id":"CVE-2025-46633","markdown":"https://insights.sbomify.com/CVE-2025-46633/index.md","name":"CVE-2025-46633","record":{"aliases":["GHSA-pjhx-jp78-8pv5"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Tenda router","requires_auth":"none","summary":"An attacker can decrypt traffic between the client and server by extracting the symmetric AES key sent in cleartext after authentication.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rx2_pro_firmware","vendor":"tenda"}],"cvss":{"score":8.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Cleartext transmission of sensitive information in the web management portal of the Tenda RX2 Pro 16.03.30.14 allows an attacker to decrypt traffic between the client and server by collecting the symmetric AES key from collected and/or observed traffic. The AES key in sent in cleartext in response to successful authentication. The IV is always EU5H62G9ICGRNI43.","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-2025-46633","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-46634"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2025-46632"},"products":["n/a"],"published":"2025-05-01","related":[{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2025-46625","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":8.2,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-46627","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":8.2,"headline":"Information disclosure in n/a","id":"CVE-2025-46634","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":7.3,"headline":"Weak cryptography in n/a","id":"CVE-2025-46626","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":7.3,"headline":"Command injection in n/a","id":"CVE-2025-46628","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":7.1,"headline":"Missing authorization in n/a","id":"CVE-2025-46635","kev_date_added":null,"published":"2025-05-01"}],"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-05-02","vendors":["n/a"]},"summary":"An attacker can decrypt traffic between the client and server by extracting the symmetric AES key sent in cleartext after authentication.","url":"https://insights.sbomify.com/CVE-2025-46633/"}