{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-5413 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-5413 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-5413 is a high-severity vulnerability in Imperva SecureSphere, published on 10 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-5413 and fix it if it is affected.\n\nWhat it is: CVE-2018-5413 is a high-severity vulnerability in Imperva SecureSphere, published on 10 Jan 2019. 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-5413 in the wild and no public exploit code.\n\nAffected product: Imperva SecureSphere. 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-5413/ (Markdown: https://insights.sbomify.com/CVE-2018-5413/index.md)","id":"CVE-2018-5413","markdown":"https://insights.sbomify.com/CVE-2018-5413/index.md","name":"CVE-2018-5413","record":{"aliases":["GHSA-w782-348v-8wjc"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Imperva SecureSphere","requires_auth":"low_privilege","summary":"Low-privileged users can add SSH keys to the admin account, enabling privilege escalation and full system control.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"securesphere","vendor":"imperva"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-250","name":"Execution with Unnecessary Privileges"}],"description":"Imperva SecureSphere running v13.0, v12.0, or v11.5 allows low privileged users to add SSH login keys to the admin user, resulting in privilege escalation.","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":"Privilege escalation in SecureSphere","id":"CVE-2018-5413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-5414"},"packages":[],"prev":{"headline":"Command injection in SecureSphere","id":"CVE-2018-5412"},"products":["SecureSphere"],"published":"2019-01-10","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2018-19646","kev_date_added":null,"published":"2018-11-28"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2018-16660","kev_date_added":null,"published":"2019-04-25"},{"cvss_score":8.1,"headline":"Command injection in SecureSphere","id":"CVE-2018-5403","kev_date_added":null,"published":"2019-01-10"},{"cvss_score":7.8,"headline":"Command injection in SecureSphere","id":"CVE-2018-5412","kev_date_added":null,"published":"2019-01-10"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2013-4091","kev_date_added":null,"published":"2013-06-28"},{"cvss_score":6.5,"headline":"File upload in n/a","id":"CVE-2013-4094","kev_date_added":null,"published":"2013-06-28"}],"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":["Imperva"]},"summary":"Low-privileged users can add SSH keys to the admin account, enabling privilege escalation and full system control.","url":"https://insights.sbomify.com/CVE-2018-5413/"}