{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15181 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-15181 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-15181 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-15181 and fix it if it is affected.\n\nWhat it is: CVE-2018-15181 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-15181 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-2018-15181/ (Markdown: https://insights.sbomify.com/CVE-2018-15181/index.md)","id":"CVE-2018-15181","markdown":"https://insights.sbomify.com/CVE-2018-15181/index.md","name":"CVE-2018-15181","record":{"aliases":["GHSA-86p3-4785-rm9c"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JioFi 4G Hotspot","requires_auth":"low_privilege","summary":"Attackers can cause a denial of service on JioFi 4G Hotspot devices by injecting XSS payloads into SSID and Security Key fields.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"4g_hotspot_m2s_firmware","vendor":"jio"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"JioFi 4G Hotspot M2S devices allow attackers to cause a denial of service (secure configuration outage) via an XSS payload in the SSID name and Security Key fields.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-08-15","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-08-15","kind":"exploitdb","ref":"45199","stars":null,"title":"JioFi 4G M2S 1.0.2 - Denial of Service (PoC)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2018-15181","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-15182"},"packages":[],"prev":{"headline":"Open redirect in n/a","id":"CVE-2018-15180"},"products":["n/a"],"published":"2018-08-09","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can cause a denial of service on JioFi 4G Hotspot devices by injecting XSS payloads into SSID and Security Key fields.","url":"https://insights.sbomify.com/CVE-2018-15181/"}