{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2008-5028 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2008-5028 yet. Limit exposure of the affected software until one is available.","what":"CVE-2008-5028 is a medium-severity vulnerability in n/a, published on 10 Nov 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2008-5028 and fix it if it is affected.\n\nWhat it is: CVE-2008-5028 is a medium-severity vulnerability in n/a, published on 10 Nov 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2008-5028 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-2008-5028/ (Markdown: https://insights.sbomify.com/CVE-2008-5028/index.md)","id":"CVE-2008-5028","markdown":"https://insights.sbomify.com/CVE-2008-5028/index.md","name":"CVE-2008-5028","record":{"aliases":["GHSA-f844-p5pg-6j6p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Nagios monitoring","requires_auth":"low_privilege","summary":"Remote attackers can exploit CSRF in Nagios to send commands and execute arbitrary programs via the monitoring process.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nagios","vendor":"nagios"},{"product":"monitor","vendor":"op5"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-site request forgery (CSRF) vulnerability in cmd.cgi in (1) Nagios 3.0.5 and (2) op5 Monitor before 4.0.1 allows remote attackers to send commands to the Nagios process, and trigger execution of arbitrary programs by this process, via unspecified HTTP requests.","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":"Cross-site request forgery in n/a","id":"CVE-2008-5028","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2008"},"n_packages":0,"n_references":18,"next":{"headline":"Denial of service in n/a","id":"CVE-2008-5029"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2008-5027"},"products":["n/a"],"published":"2008-11-10","related":[{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2002-1959","kev_date_added":null,"published":"2005-06-28"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2016-0726","kev_date_added":null,"published":"2017-06-06"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2008-7313","kev_date_added":null,"published":"2017-03-31"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2014-5009","kev_date_added":null,"published":"2017-03-31"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2016-9565","kev_date_added":null,"published":"2016-12-15"},{"cvss_score":8.8,"headline":"Nagios Log Server 2.1.3 has CSRF.","id":"CVE-2020-6585","kev_date_added":null,"published":"2020-03-16"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2016-10089","kev_date_added":null,"published":"2017-02-15"}],"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-07","vendors":["n/a"]},"summary":"Remote attackers can exploit CSRF in Nagios to send commands and execute arbitrary programs via the monitoring process.","url":"https://insights.sbomify.com/CVE-2008-5028/"}