{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-0519 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-0519 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-0519 is a medium-severity vulnerability in n/a, published on 10 May 2013. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-0519 and fix it if it is affected.\n\nWhat it is: CVE-2013-0519 is a medium-severity vulnerability in n/a, published on 10 May 2013. 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-2013-0519 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-2013-0519/ (Markdown: https://insights.sbomify.com/CVE-2013-0519/index.md)","id":"CVE-2013-0519","markdown":"https://insights.sbomify.com/CVE-2013-0519/index.md","name":"CVE-2013-0519","record":{"aliases":["GHSA-x2c5-cm4v-4x63"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Secure Proxy Server","requires_auth":"none","summary":"Remote attackers can obtain sensitive version information from HTTP headers and page titles in IBM Sterling Secure Proxy.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_secure_proxy","vendor":"ibm"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"IBM Sterling Secure Proxy 3.2.0 and 3.3.01 before 3.3.01.23 Interim Fix 1, 3.4.0 before 3.4.0.6 Interim Fix 1, and 3.4.1 before 3.4.1.7 provides web-server version data in (1) an unspecified page title and (2) an unspecified HTTP header field, which allows remote attackers to obtain potentially sensitive information by reading a version string.","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":"Information disclosure in n/a","id":"CVE-2013-0519","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2013"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2013-0520"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2013-0518"},"products":["n/a"],"published":"2013-05-10","related":[{"cvss_score":9.1,"headline":"IBM Sterling Secure Proxy improper input validation","id":"CVE-2024-38337","kev_date_added":null,"published":"2025-01-19"},{"cvss_score":9.1,"headline":"IBM Sterling Secure Proxy improper input validation","id":"CVE-2024-41783","kev_date_added":null,"published":"2025-01-19"},{"cvss_score":7.5,"headline":"IBM Sterling Secure Proxy directory traversal","id":"CVE-2024-41784","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2016-6023","kev_date_added":null,"published":"2016-10-06"},{"cvss_score":6.1,"headline":"IBM Secure Proxy cross-site scripting","id":"CVE-2023-47162","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":6.1,"headline":"IBM Secure Proxy cross-site scripting","id":"CVE-2023-47699","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":6.1,"headline":"Security feature bypass in n/a","id":"CVE-2016-6027","kev_date_added":null,"published":"2016-10-06"}],"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-06","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive version information from HTTP headers and page titles in IBM Sterling Secure Proxy.","url":"https://insights.sbomify.com/CVE-2013-0519/"}