{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-4562 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-4562 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-4562 is a medium-severity server-side request forgery vulnerability in Progress Whatsup Gold, published on 14 May 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-4562 and fix it if it is affected.\n\nWhat it is: CVE-2024-4562 is a medium-severity server-side request forgery vulnerability in Progress Whatsup Gold, published on 14 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-4562 in the wild and no public exploit code.\n\nAffected product: Progress Whatsup Gold. 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-2024-4562/ (Markdown: https://insights.sbomify.com/CVE-2024-4562/index.md)","id":"CVE-2024-4562","markdown":"https://insights.sbomify.com/CVE-2024-4562/index.md","name":"CVE-2024-4562","record":{"aliases":["GHSA-q8gh-g2x4-x4cm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Network monitoring software","requires_auth":"low_privilege","summary":"Authenticated users can exploit an SSRF vulnerability in HTTP monitoring to access internal resources due to missing authorization checks.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ProgressSoftware","cpe":[{"product":"whatsup_gold","vendor":"progress"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"In WhatsUp Gold versions released before 2023.1.2 , \n\nan SSRF vulnerability exists in Whatsup Gold's \n\nIssue exists in the HTTP Monitoring functionality.  \n\nDue to the lack of proper authorization, any authenticated user can access the HTTP monitoring functionality, what leads to the Server Side Request Forgery.","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":"WhatsUp Gold Server-Side Request Forgery Information Disclosure Vulnerability via HttpMonitorSettings","id":"CVE-2024-4562","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"progress:whatsup_gold","products":["progress:whatsup_gold"],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"The Progress MOVEit Automation Configuration Export Function Uses a Cryptographic Method with Insufficient Bit Length","id":"CVE-2024-4563"},"packages":[],"prev":{"headline":"WhatsUp Gold Server-Side Request Forgery Information Disclosure Vulnerability via FaviconController","id":"CVE-2024-4561"},"products":["WhatsUp Gold"],"published":"2024-05-14","related":[{"cvss_score":9.8,"headline":"Progress WhatsUp Gold SQL Injection","id":"CVE-2024-6670","kev_date_added":"2024-09-16","published":"2024-08-29"},{"cvss_score":9.8,"headline":"Progress WhatsUp Gold Path Traversal","id":"CVE-2024-4885","kev_date_added":"2025-03-03","published":"2024-06-25"},{"cvss_score":9.8,"headline":"WhatsUp Gold WriteDataFile Directory Traversal Remote Code Execution Vulnerability","id":"CVE-2024-46909","kev_date_added":null,"published":"2024-12-02"},{"cvss_score":9.8,"headline":"WhatsUp Gold Registry Overwrite Remote Code Execution Vulnerability","id":"CVE-2024-8785","kev_date_added":null,"published":"2024-12-02"},{"cvss_score":9.8,"headline":"WhatsUp Gold getReport Missing Authentication Authentication Bypass Vulnerability","id":"CVE-2024-7763","kev_date_added":null,"published":"2024-10-24"},{"cvss_score":9.8,"headline":"WhatsUp Gold GetStatisticalMonitorList SQL Injection Authentication Bypass Vulnerability","id":"CVE-2024-6671","kev_date_added":null,"published":"2024-08-29"},{"cvss_score":9.8,"headline":"WhatsUp Gold WriteDataFile Directory Traversal Remote Code Execution Vulnerability","id":"CVE-2024-4883","kev_date_added":null,"published":"2024-06-25"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Progress Software Corporation"]},"summary":"Authenticated users can exploit an SSRF vulnerability in HTTP monitoring to access internal resources due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2024-4562/"}