{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17503 exists.","fix":"No fix has been published for CVE-2019-17503 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17503 is a medium-severity vulnerability in n/a, published on 11 Oct 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-2019-17503 and fix it if it is affected.\n\nWhat it is: CVE-2019-17503 is a medium-severity vulnerability in n/a, published on 11 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17503 exists.\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-2019-17503/ (Markdown: https://insights.sbomify.com/CVE-2019-17503/index.md)","id":"CVE-2019-17503","markdown":"https://insights.sbomify.com/CVE-2019-17503/index.md","name":"CVE-2019-17503","record":{"aliases":["GHSA-2fff-jm87-282r"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kirona DRS","requires_auth":"none","summary":"Unauthenticated attackers can access a batch file exposing sensitive SQL database schema details in Kirona Dynamic Resource Scheduling.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dynamic_resource_scheduling","vendor":"kirona"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-425","name":"Direct Request"}],"description":"An issue was discovered in Kirona Dynamic Resource Scheduling (DRS) 5.5.3.5. An unauthenticated user can access /osm/REGISTER.cmd (aka /osm_tiles/REGISTER.cmd) directly: it contains sensitive information about the database through the SQL queries within this batch file. This file exposes SQL database information such as database version, table name, column name, etc.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-10-14","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":"2019-10-14","kind":"exploitdb","ref":"47498","stars":null,"title":"Kirona-DRS 5.5.3.5 - Information Disclosure"},{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-17503.yaml","stars":null,"title":"Kirona Dynamic Resource Scheduler - Information Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2019-17503","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-17504"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2019-17502"},"products":["n/a"],"published":"2019-10-11","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-17504","kev_date_added":null,"published":"2019-10-11"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Unauthenticated attackers can access a batch file exposing sensitive SQL database schema details in Kirona Dynamic Resource Scheduling.","url":"https://insights.sbomify.com/CVE-2019-17503/"}