{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2005-2779 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-2779 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2779 is a medium-severity vulnerability in n/a, published on 2 Sep 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2005-2779 and fix it if it is affected.\n\nWhat it is: CVE-2005-2779 is a medium-severity vulnerability in n/a, published on 2 Sep 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2005-2779 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-2005-2779/ (Markdown: https://insights.sbomify.com/CVE-2005-2779/index.md)","id":"CVE-2005-2779","markdown":"https://insights.sbomify.com/CVE-2005-2779/index.md","name":"CVE-2005-2779","record":{"aliases":["GHSA-6rg7-w25r-589m"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Online Banking System","requires_auth":"low_privilege","summary":"Attackers can intercept TAN numbers via MITM attacks during transactions, enabling account takeover in the iTAN Online-Banking Security System.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"The iTAN Online-Banking Security System allows remote attackers to obtain TAN numbers via a man-in-the-middle (MITM) attack while the transaction is taking place, which facilitates a \"phishing\" attack.","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":"Security feature bypass in n/a","id":"CVE-2005-2779","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2005"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-2780"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2005-2778"},"products":["n/a"],"published":"2005-09-02","related":[],"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":"Attackers can intercept TAN numbers via MITM attacks during transactions, enabling account takeover in the iTAN Online-Banking Security System.","url":"https://insights.sbomify.com/CVE-2005-2779/"}