{"answers":{"affected":"2 open source packages ship an affected version, including email-existence. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-25049 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-25049 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-25049 is a low-severity denial of service vulnerability in email-existence, published on 27 Dec 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-25049 and fix it if it is affected.\n\nWhat it is: CVE-2018-25049 is a low-severity denial of service vulnerability in email-existence, published on 27 Dec 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-25049 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- email-existence (npm): affected all versions up to 0.1.6; no fix listed\n- email-existence (npm): affected all versions up to 0.1.6; no fix listed\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-2018-25049/ (Markdown: https://insights.sbomify.com/CVE-2018-25049/index.md)","id":"CVE-2018-25049","markdown":"https://insights.sbomify.com/CVE-2018-25049/index.md","name":"CVE-2018-25049","record":{"aliases":["GHSA-p27h-4cpf-fw48"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"npm email validation library","requires_auth":"low_privilege","summary":"An attacker can cause a denial of service in the email-existence library by triggering inefficient regular expression complexity.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"email-existence","vendor":"email-existence_project"}],"cvss":{"score":3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"A vulnerability was found in email-existence. It has been rated as problematic. Affected by this issue is some unknown functionality of the file index.js. The manipulation leads to inefficient regular expression complexity. The name of the patch is 0029ba71b6ad0d8ec0baa2ecc6256d038bdd9b56. It is recommended to apply a patch to fix this issue. VDB-216854 is the identifier assigned to this vulnerability.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"email-existence index.js redos","id":"CVE-2018-25049","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":2,"n_references":4,"next":{"headline":"Harvest Chosen abstract-chosen.coffee AbstractChosen cross site scripting","id":"CVE-2018-25050"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.6"],"package":"email-existence","purl":null,"source":"GHSA-p27h-4cpf-fw48"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.6"],"package":"email-existence","purl":"pkg:npm/email-existence","source":"GHSA-p27h-4cpf-fw48"}],"prev":{"headline":"Codesys Runtime Improper Limitation of a Pathname","id":"CVE-2018-25048"},"products":["email-existence"],"published":"2022-12-27","related":[],"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":"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-04-11","vendors":["n/a"]},"summary":"An attacker can cause a denial of service in the email-existence library by triggering inefficient regular expression complexity.","url":"https://insights.sbomify.com/CVE-2018-25049/"}