{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-1000411 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1000411 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1000411 is a high-severity denial of service vulnerability in n/a, published on 31 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1000411 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000411 is a high-severity denial of service vulnerability in n/a, published on 31 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1000411 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-1000411/ (Markdown: https://insights.sbomify.com/CVE-2017-1000411/index.md)","id":"CVE-2017-1000411","markdown":"https://insights.sbomify.com/CVE-2017-1000411/index.md","name":"CVE-2017-1000411","record":{"aliases":["GHSA-wrhh-rh53-55jj"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"SDN Controller","requires_auth":"none","summary":"Attackers can crash the OpenDayLight controller by sending multiple expired flows that consume memory in the configuration datastore.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opendaylight","vendor":"opendaylight"},{"product":"openflow","vendor":"opendaylight"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-404","name":"Improper Resource Shutdown or Release"}],"description":"OpenFlow Plugin and OpenDayLight Controller versions Nitrogen, Carbon, Boron, Robert Varga, Anil Vishnoi contain a flaw when multiple 'expired' flows take up the memory resource of CONFIG DATASTORE which leads to CONTROLLER shutdown. If multiple different flows with 'idle-timeout' and 'hard-timeout' are sent to the Openflow Plugin REST API, the expired flows will eventually crash the controller once its resource allocations set with the JVM size are exceeded. Although the installed flows (with timeout set) are removed from network (and thus also from controller's operations DS), the expired entries are still present in CONFIG DS. The attack can originate both from NORTH or SOUTH. The above description is for a north bound attack. A south bound attack can originate when an attacker attempts a flow flooding attack and since flows come with timeouts, the attack is not successful. However, the attacker will now be successful in CONTROLLER overflow attack (resource consumption). Although, the network (actual flow tables) and operational DS are only (~)1% occupied, the controller requests for resource consumption. This happens because the installed flows get removed from the network upon timeout.","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-1000411","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2017-1000412"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2017-1000410"},"products":["n/a"],"published":"2018-01-31","related":[{"cvss_score":9.8,"headline":"Opendaylight will authenticate any username and password combination","id":"CVE-2015-1778","kev_date_added":null,"published":"2017-06-27"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-1000357","kev_date_added":null,"published":"2017-04-24"},{"cvss_score":7.5,"headline":"OpenDaylight Controller DoS","id":"CVE-2017-1000361","kev_date_added":null,"published":"2017-04-24"},{"cvss_score":6.8,"headline":"XML external entity in n/a","id":"CVE-2014-5035","kev_date_added":null,"published":"2014-08-26"},{"cvss_score":6.5,"headline":"Null dereference in n/a","id":"CVE-2017-1000358","kev_date_added":null,"published":"2017-04-24"},{"cvss_score":5.3,"headline":"Denial of service in n/a","id":"CVE-2017-1000359","kev_date_added":null,"published":"2017-04-24"}],"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":"Attackers can crash the OpenDayLight controller by sending multiple expired flows that consume memory in the configuration datastore.","url":"https://insights.sbomify.com/CVE-2017-1000411/"}