{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2017-17259 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17259 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17259 is a vulnerability, published on 5 Mar 2019."},"fix_prompt":"Check this codebase for CVE-2017-17259 and fix it if it is affected.\n\nWhat it is: CVE-2017-17259 is a vulnerability, published on 5 Mar 2019. \nExploitation: There is no known exploitation of CVE-2017-17259 in the wild and no public exploit code.\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-17259/ (Markdown: https://insights.sbomify.com/CVE-2017-17259/index.md)","id":"CVE-2017-17259","markdown":"https://insights.sbomify.com/CVE-2017-17259/index.md","name":"CVE-2017-17259","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"huawei","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2017. Notes: none","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":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2017-17259","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2017"},"n_packages":0,"n_references":0,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2017-17260"},"packages":[],"prev":{"headline":"Other in AR120-S, AR1200, AR1200-S, AR150, AR150-S, AR160, AR200, AR200-S, AR2200, AR2200-S, AR3200, AR3600, AR510, DP300, IPS Module, NGFW Module, NIP6300, NIP6600, NIP6800, NetEngine16EX, RSE6500, SRG1300, SRG2300, SRG3300, SVN5600, SVN5800, SVN5800-C, SeMG9811, Secospace USG6300, Secospace USG6500, Secospace USG6600, TE30, TE40, TE50, TE60, TP3106, TP3206, USG6000V, USG9500, USG9520, USG9560, USG9580, VP9660, ViewPoint 8660, ViewPoint 9030","id":"CVE-2017-17258"},"products":[],"published":"2019-03-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2019-03-05","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2017-17259/"}