From CVE Record to External Exposure
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Solr. The Solr Metrics API publishes all unprotected environment variables available to each Apache Solr instance. Users are able to specify which environment variables to hide, however, the default list is designed to work for known secret Java system properties. Environment variables cannot be strictly defined in Solr, like Java system properties can be, and may be set for the entire host, unlike Java system properties which are set per-Java-proccess. The Solr Metrics API is protected by the "metrics-read" permission. Therefore, Solr Clouds with Authorization setup will only be vulnerable via users with the "metrics-read" permission. This issue affects Apache Solr: from 9.0.0 before 9.3.0. Users are recommended to upgrade to version 9.3.0 or later, in which environment variables are not published via ...
Solr vulnerability should be triaged by matching the affected vendor and product to live, internet-facing assets rather than treating the CVE as an abstract feed item. ThreatPort focuses on the first question that budget-constrained IT leaders and CISOs ask: what can an outside observer find today, how severe is it, and what should be fixed first?
Known Exploitation Record
- Known ransomware campaign use
- Not recorded
- EPSS exploitation probability
- 68.66% (99p)
- CVSS base score
- 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)
- Disclosed
- 2024-01-15
- Weakness type
- CWE-200
Source: CISA Known Exploited Vulnerabilities catalog and FIRST.org EPSS.
What ThreatPort Checks
The output is intentionally practical: ownership clues, risk context, remediation hints, and repeatable evidence that can be shared with technical teams or leadership. It is not positioned as magic compliance automation or a replacement for human security judgment.
Lean security teams rarely need another broad vulnerability list. They need to know whether an exposed endpoint, an expired certificate, a weak DNS setting, or a CVE-linked service is likely to affect the systems they actually run. ThreatPort scans from the outside in, ranks what it finds by real reachability rather than raw CVSS, and hands back evidence a team can act on the same day.
Route-Specific Evidence Profile
CVE-2023-50290 affects Apache Solr, a CWE-200 weakness. Disclosed 2024-01-15. This page exists to answer one question: is anything you own externally reachable and running it.
Assets This Page Should Care About
Signals Worth Prioritizing
What Should Be Reviewed First in This Context?
For teams running Apache Solr, the first step is to validate internet-facing assets with business relevance instead of producing a generic vulnerability list.
Action Checklist
- Confirm whether Solr is present on any public domain, subdomain, API, or admin surface.
- Prioritize MEDIUM exposure only when the affected service is reachable or business-critical.
- Patch, disable, isolate, or put compensating controls in front of the affected service.
- Re-scan after remediation to capture before-and-after evidence for technical teams or leadership.
Context-Aware Next Fixes
- Verify ownership of exposed assets
- Close unnecessary public services
- Remediate the highest-confidence exposed findings first, then re-scan to prove closure.
Useful evidence for this context usually maps to ISO 27001, SOC 2, vendor security reviews. ThreatPort keeps the language cautious: this is operational security evidence, not a legal certification or a guarantee that every auditor will accept a generated report without review.