{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2006-5484 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-5484 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-5484 is a medium-severity vulnerability in n/a, published on 24 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-5484 and fix it if it is affected.\n\nWhat it is: CVE-2006-5484 is a medium-severity vulnerability in n/a, published on 24 Oct 2006. 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-2006-5484 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-2006-5484/ (Markdown: https://insights.sbomify.com/CVE-2006-5484/index.md)","id":"CVE-2006-5484","markdown":"https://insights.sbomify.com/CVE-2006-5484/index.md","name":"CVE-2006-5484","record":{"aliases":["GHSA-f6g8-8p5j-hphv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SSH Tectia","requires_auth":"none","summary":"Remote attackers can forge PKCS #1 v1.5 signatures when RSA keys with exponent 3 are used, bypassing certificate verification in SSH Tectia products.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tectia_client","vendor":"ssh"},{"product":"tectia_connector","vendor":"ssh"},{"product":"tectia_manager","vendor":"ssh"},{"product":"tectia_server","vendor":"ssh"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"SSH Tectia Client/Server/Connector 5.1.0 and earlier, Manager 2.2.0 and earlier, and other products, when using an RSA key with exponent 3, removes PKCS-1 padding before generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents Tectia from correctly verifying X.509 and other certificates that use PKCS #1, a similar issue to CVE-2006-4339.","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-2006-5484","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2006"},"n_packages":0,"n_references":6,"next":{"headline":"Code injection in n/a","id":"CVE-2006-5485"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2006-5483"},"products":["n/a"],"published":"2006-10-24","related":[{"cvss_score":8.8,"headline":"SSH Tectia Client and Server before 6.4.19 on Windows have weak key generation.","id":"CVE-2021-27891","kev_date_added":null,"published":"2021-03-15"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-27892","kev_date_added":null,"published":"2021-03-15"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2007-5616","kev_date_added":null,"published":"2008-01-09"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2006-4315","kev_date_added":null,"published":"2006-08-23"},{"cvss_score":7,"headline":"Privilege escalation in n/a","id":"CVE-2021-27893","kev_date_added":null,"published":"2021-03-15"}],"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-07","vendors":["n/a"]},"summary":"Remote attackers can forge PKCS #1 v1.5 signatures when RSA keys with exponent 3 are used, bypassing certificate verification in SSH Tectia products.","url":"https://insights.sbomify.com/CVE-2006-5484/"}