CVE-2019-15041
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJetBrains YouTrack versions before 2019.1.52545 allowed unbounded URL whitelisting because of Inclusion of Functionality from an Untrusted Control Sphere.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceJetBrains YouTrack versions before 2019.1.52545 contain a vulnerability where URL whitelisting can be configured without proper bounds, allowing inclusion of functionality from untrusted external sources. This stems from the application trusting arbitrary URLs that could deliver malicious content or code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2019.1.52545CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed YouTrack versionLog into YouTrack as administrator and navigate to Administration > About, or check the version displayed in the footer of the web interface. Compare this version number to 2019.1.52545.Affected if The installed version is below 2019.1.52545 (for example, 2019.1.50000).
-
Locate URL whitelist configurationIn the YouTrack administration interface, go to System > URL WhiteList or Settings > Security > Allowed URLs. If using a configuration file, locate the file where whitelist URLs are stored.Affected if URL whitelist settings are present and configurable in the environment.
-
Inspect whitelist for untrusted external URLsReview all URLs listed in the whitelist configuration. Check for any URLs pointing to domains or IP addresses that are not internally controlled or explicitly trusted.Affected if The whitelist contains URLs from untrusted or external sources that are not verified internal resources.
-
Verify if whitelist accepts arbitrary URLsAttempt to add a test URL to the whitelist configuration to confirm whether the system allows inclusion of any URL without proper bounds checking or domain validation.Affected if The system permits adding arbitrary URLs to the whitelist without restriction or validation.
A user is affected if their YouTrack installation is version 2019.1.52545 or earlier AND has a URL whitelist configured that includes untrusted or external URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2019.1.52545
Update YouTrack to version 2019.1.52545 or later. If immediate patching is not possible, audit and restrict the URL whitelist to only trusted, internal sources.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15041 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15041 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data