{"answers":{"affected":"2 open source packages ship an affected version, including rack-cors. It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-11173 in the wild and no public exploit code.","fix":"Upgrade rack-cors to 0.4.1 or later.","what":"CVE-2017-11173 is a high-severity vulnerability in Debian Debian Linux, published on 13 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-11173 and fix it if it is affected.\n\nWhat it is: CVE-2017-11173 is a high-severity vulnerability in Debian Debian Linux, published on 13 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-11173 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rack-cors (RubyGems): affected all versions; fixed in 0.4.1\n- rack-cors (RubyGems): affected all versions; fixed in 0.4.1\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-2017-11173/ (Markdown: https://insights.sbomify.com/CVE-2017-11173/index.md)","id":"CVE-2017-11173","markdown":"https://insights.sbomify.com/CVE-2017-11173/index.md","name":"CVE-2017-11173","record":{"aliases":["DEBIAN-CVE-2017-11173","DSA-3931-1","GHSA-2j9c-9vmv-7m39","UBUNTU-CVE-2017-11173"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby CORS library","requires_auth":"none","summary":"A regex flaw in rack-cors allows malicious sites to bypass CORS restrictions, enabling unauthorized cross-origin requests if specific domain configurations are used.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"debian_linux","vendor":"debian"},{"product":"rack-cors","vendor":"rack-cors_project"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted example.com domain name and not the malicious example.net domain name, then example.com.example.net (as well as example.com-example.net) would be inadvertently allowed.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request","id":"CVE-2017-11173","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":"debian:debian_linux","products":["debian:debian_linux"],"type":"security_feature_bypass","year":"2017"},"n_packages":2,"n_references":4,"next":{"headline":"SQL injection in n/a","id":"CVE-2017-11174"},"packages":[{"ecosystem":"RubyGems","fixed":["0.4.1"],"introduced":["0"],"last_affected":[],"package":"rack-cors","purl":null,"source":"GHSA-2j9c-9vmv-7m39"},{"ecosystem":"RubyGems","fixed":["0.4.1"],"introduced":["0"],"last_affected":[],"package":"rack-cors","purl":"pkg:gem/rack-cors","source":"GHSA-2j9c-9vmv-7m39"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-11171"},"products":["n/a"],"published":"2017-07-13","related":[{"cvss_score":10,"headline":"ProFTPD Improper Access Control","id":"CVE-2015-3306","kev_date_added":"2026-10-08","published":"2015-05-18"},{"cvss_score":9.9,"headline":"RoundCube Webmail Deserialization of Untrusted Data","id":"CVE-2025-49113","kev_date_added":"2026-02-20","published":"2025-06-02"},{"cvss_score":9.8,"headline":"GNU InetUtils Argument Injection","id":"CVE-2026-24061","kev_date_added":"2026-01-26","published":"2026-01-21"},{"cvss_score":9.8,"headline":"Linux Kernel Improper Check for Unusual or Exceptional Conditions","id":"CVE-2025-39682","kev_date_added":"2026-09-18","published":"2025-09-05"},{"cvss_score":9.8,"headline":"Mozilla Firefox Use-After-Free","id":"CVE-2024-9680","kev_date_added":"2024-10-15","published":"2024-10-09"},{"cvss_score":9.8,"headline":"RARLAB UnRAR Directory Traversal","id":"CVE-2022-30333","kev_date_added":"2022-08-09","published":"2022-05-09"},{"cvss_score":9.8,"headline":"Roundcube Webmail SQL Injection","id":"CVE-2021-44026","kev_date_added":"2023-06-22","published":"2021-11-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-05","vendors":["n/a"]},"summary":"A regex flaw in rack-cors allows malicious sites to bypass CORS restrictions, enabling unauthorized cross-origin requests if specific domain configurations are used.","url":"https://insights.sbomify.com/CVE-2017-11173/"}