{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2017-8330 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8330 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8330 is a medium-severity denial of service vulnerability in n/a, published on 18 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8330 and fix it if it is affected.\n\nWhat it is: CVE-2017-8330 is a medium-severity denial of service vulnerability in n/a, published on 18 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-8330 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-2017-8330/ (Markdown: https://insights.sbomify.com/CVE-2017-8330/index.md)","id":"CVE-2017-8330","markdown":"https://insights.sbomify.com/CVE-2017-8330/index.md","name":"CVE-2017-8330","record":{"aliases":["GHSA-jfgg-vc2q-w48v"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Securifi Almond router","requires_auth":"none","summary":"A remote attacker can crash the miniupnpd process on Securifi Almond routers by sending a large payload to the NewInMessage SOAP parameter.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"almond\\+firmware","vendor":"securifi"},{"product":"almond_2015_firmware","vendor":"securifi"},{"product":"almond_firmware","vendor":"securifi"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered on Securifi Almond, Almond+, and Almond 2015 devices with firmware AL-R096. The device provides a UPnP functionality for devices to interface with the router and interact with the device. It seems that the \"NewInMessage\" SOAP parameter passed with a huge payload results in crashing the process. If the firmware version AL-R096 is dissected using binwalk tool, we obtain a cpio-root archive which contains the filesystem set up on the device that contains all the binaries. The binary \"miniupnpd\" is the one that has the vulnerable function that receives the values sent by the SOAP request. If we open this binary in IDA-pro we will notice that this follows a MIPS little endian format. The function WscDevPutMessage at address 0x0041DBB8 in IDA pro is identified to be receiving the values sent in the SOAP request. The SOAP parameter \"NewInMesage\" received at address 0x0041DC30 causes the miniupnpd process to finally crash when a second request is sent to the same process.","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":"Denial of service in n/a","id":"CVE-2017-8330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2017-8331"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-8329"},"products":["n/a"],"published":"2019-06-18","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-8328","kev_date_added":null,"published":"2019-06-18"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-8331","kev_date_added":null,"published":"2019-06-18"},{"cvss_score":8.8,"headline":"Cross-site scripting in n/a","id":"CVE-2017-8332","kev_date_added":null,"published":"2019-06-18"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-8333","kev_date_added":null,"published":"2019-06-18"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-8336","kev_date_added":null,"published":"2019-06-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-8337","kev_date_added":null,"published":"2019-06-18"},{"cvss_score":8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-8334","kev_date_added":null,"published":"2019-06-18"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A remote attacker can crash the miniupnpd process on Securifi Almond routers by sending a large payload to the NewInMessage SOAP parameter.","url":"https://insights.sbomify.com/CVE-2017-8330/"}