{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19513 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19513 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19513 is a high-severity vulnerability in n/a, published on 17 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-19513 and fix it if it is affected.\n\nWhat it is: CVE-2018-19513 is a high-severity vulnerability in n/a, published on 17 Mar 2019. 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-2018-19513 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-2018-19513/ (Markdown: https://insights.sbomify.com/CVE-2018-19513/index.md)","id":"CVE-2018-19513","markdown":"https://insights.sbomify.com/CVE-2018-19513/index.md","name":"CVE-2018-19513","record":{"aliases":["GHSA-2pvh-xf99-r989"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Webgalamb CMS","requires_auth":"none","summary":"Attackers can access predictable log files containing sensitive email addresses and SQL error details, facilitating further attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"webgalamb","vendor":"ens"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"In Webgalamb through 7.0, log files are exposed to the internet with predictable files/logs/sql_error_log/YYYY-MM-DD-sql_error_log.log filenames. The log file could contain sensitive client data (email addresses) and also facilitates exploitation of SQL injection errors.","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-2018-19513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2018-19514"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2018-19512"},"products":["n/a"],"published":"2019-03-17","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-19510","kev_date_added":null,"published":"2019-03-17"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2018-19514","kev_date_added":null,"published":"2019-03-17"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2018-19515","kev_date_added":null,"published":"2019-03-17"},{"cvss_score":7.2,"headline":"Path traversal in n/a","id":"CVE-2018-19512","kev_date_added":null,"published":"2019-03-17"},{"cvss_score":6.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-19511","kev_date_added":null,"published":"2019-03-17"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-19509","kev_date_added":null,"published":"2019-03-17"}],"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":["n/a"]},"summary":"Attackers can access predictable log files containing sensitive email addresses and SQL error details, facilitating further attacks.","url":"https://insights.sbomify.com/CVE-2018-19513/"}