{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41812 exists.","fix":"No fix has been published for CVE-2024-41812 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41812 is a high-severity server-side request forgery vulnerability in txtdot, published on 26 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-41812 and fix it if it is affected.\n\nWhat it is: CVE-2024-41812 is a high-severity server-side request forgery vulnerability in txtdot, published on 26 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41812 exists.\n\nAffected product: txtdot. 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-41812/ (Markdown: https://insights.sbomify.com/CVE-2024-41812/index.md)","id":"CVE-2024-41812","markdown":"https://insights.sbomify.com/CVE-2024-41812/index.md","name":"CVE-2024-41812","record":{"aliases":["GHSA-4gj5-xj97-j8fp"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HTTP proxy service","requires_auth":"none","summary":"Remote attackers can exploit the /get route to send arbitrary HTTP requests and access internal network resources via the txtdot proxy.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"txtdot","vendor":"txtdot"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"txtdot is an HTTP proxy that parses only text, links, and pictures from pages, removing ads and heavy scripts. Prior to version 1.7.0, a Server-Side Request Forgery (SSRF) vulnerability in the `/get` route of txtdot allows remote attackers to use the server as a proxy to send HTTP GET requests to arbitrary targets and retrieve information in the internal network. Version 1.7.0 prevents displaying the response of forged requests, but the requests can still be sent. For complete mitigation, a firewall between txtdot and other internal network resources should be set.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"txtdot SSRF vulnerability in /get","id":"CVE-2024-41812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"txtdot SSRF vulnerability in /proxy","id":"CVE-2024-41813"},"packages":[],"prev":{"headline":"ipl/web susceptible to Cross-Site Request Forgery (CSRF)","id":"CVE-2024-41811"},"products":["txtdot"],"published":"2024-07-26","related":[{"cvss_score":7.5,"headline":"txtdot SSRF vulnerability in /proxy","id":"CVE-2024-41813","kev_date_added":null,"published":"2024-07-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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["TxtDot"]},"summary":"Remote attackers can exploit the /get route to send arbitrary HTTP requests and access internal network resources via the txtdot proxy.","url":"https://insights.sbomify.com/CVE-2024-41812/"}