CVE-2019-17503

MEDIUMNVD 5.39.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 90% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 49%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
9.0(high)
EPSS
98.7%
KEV
Not listed

Published

October 11, 2019

Last Modified

November 21, 2024

References (4)

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-11 08:24 UTCEPSS rescore
  3. 2026-07-09 19:06 UTCEPSS rescore
  4. 2026-07-08 15:11 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-01 15:03 UTCEPSS rescore
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-06-29 14:03 UTCEPSS rescore
  10. 2026-06-28 04:54 UTCEPSS rescore
  11. 2026-06-28 04:54 UTCEPSS rescore
  12. 2026-06-27 03:06 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 14:03 UTCEPSS rescore
  16. 2026-06-24 14:03 UTCEPSS rescore
  17. 2026-06-23 21:31 UTCEPSS rescore
  18. 2026-06-23 21:30 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-21 01:57 UTCEPSS rescore
  21. 2026-06-18 17:50 UTCEPSS rescore
  22. 2026-06-17 17:50 UTCEPSS rescore
  23. 2026-06-16 17:50 UTCEPSS rescore
  24. 2026-06-15 17:45 UTCEPSS rescore
  25. 2026-06-13 22:58 UTCEPSS rescore
Show 16 more
  1. 2026-06-12 23:09 UTCEPSS rescore
  2. 2026-06-10 22:16 UTCEPSS rescore
  3. 2026-06-10 13:19 UTCEPSS rescore
  4. 2026-06-08 14:15 UTCEPSS rescore
  5. 2026-06-05 22:45 UTCEPSS rescore
  6. 2026-06-05 22:45 UTCEPSS rescore
  7. 2026-06-01 13:50 UTCEPSS rescore
  8. 2026-06-01 13:50 UTCEPSS rescore
  9. 2026-05-31 22:29 UTCEPSS rescore
  10. 2026-05-31 22:29 UTCEPSS rescore
  11. 2026-05-31 00:14 UTCEPSS rescore
  12. 2026-05-31 00:14 UTCEPSS rescore
  13. 2026-05-29 13:42 UTCEPSS rescore
  14. 2026-05-28 13:43 UTCEPSS rescore
  15. 2026-05-27 13:05 UTCEG score recompute
  16. 2026-05-27 13:05 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-47498
    First seen Oct 14, 2019

    Kirona-DRS 5.5.3.5 - Information Disclosure

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-17503.yaml
    First seen Jan 1, 2019

    Kirona Dynamic Resource Scheduler - Information Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-17503?
CVE-2019-17503 is a medium vulnerability published on October 11, 2019. 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…
When was CVE-2019-17503 disclosed?
CVE-2019-17503 was first published in the National Vulnerability Database on October 11, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-17503 actively exploited?
CVE-2019-17503 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-17503?
CVE-2019-17503 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2019-17503?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-17503, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-17503

Explore →

Is Your Infrastructure Affected by CVE-2019-17503?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs