CVE-2023-50290: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in Apache Software Foundation Apache Solr
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 the Metrics API.
AI Analysis
Technical Summary
CVE-2023-50290 is a vulnerability in Apache Solr versions 9.0.0 up to but not including 9.3.0, classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). The issue arises from the Solr Metrics API, which by default publishes all unprotected environment variables available to each Solr instance. While users can specify environment variables to hide, the default protections only cover known secret Java system properties. Environment variables differ from Java system properties in that they are set at the host level rather than per Java process, making it difficult to strictly define or restrict them within Solr. This results in potentially sensitive environment variables being exposed via the Metrics API. Access to this API requires the "metrics-read" permission, so only users with this permission can exploit the vulnerability. In environments where Solr Cloud is configured with authorization, the risk is limited to users granted this permission. The vulnerability does not require user interaction and can be exploited remotely over the network. The CVSS v3.1 base score is 6.5 (medium severity), reflecting high confidentiality impact but no impact on integrity or availability. The recommended remediation is to upgrade to Apache Solr version 9.3.0 or later, where environment variables are no longer published via the Metrics API, effectively mitigating the issue. No known exploits are currently reported in the wild.
Potential Impact
For European organizations using Apache Solr versions 9.0.0 to before 9.3.0, this vulnerability poses a significant risk of sensitive information leakage. Environment variables often contain credentials, API keys, or configuration details that could facilitate further attacks if disclosed to unauthorized users. Although exploitation requires "metrics-read" permission, insider threats or compromised accounts with this permission could lead to unauthorized data exposure. This could result in loss of confidentiality, regulatory non-compliance (e.g., GDPR violations if personal data is indirectly exposed), and potential reputational damage. Since Solr is widely used in enterprise search and big data applications, exposure of environment variables could aid attackers in lateral movement or privilege escalation within affected organizations. The vulnerability does not affect system integrity or availability directly but undermines trust in system security and confidentiality.
Mitigation Recommendations
1. Upgrade Apache Solr to version 9.3.0 or later immediately, as this version removes environment variable exposure via the Metrics API. 2. Review and restrict the assignment of the "metrics-read" permission to only trusted and necessary users or service accounts. 3. Audit environment variables on hosts running Solr to minimize sensitive data exposure; avoid storing secrets in environment variables where possible. 4. Implement network segmentation and access controls to limit who can reach the Solr Metrics API endpoints. 5. Monitor and log usage of the Metrics API to detect unusual access patterns or unauthorized attempts. 6. Consider additional application-layer encryption or secrets management solutions to reduce reliance on environment variables for sensitive data. 7. Conduct regular security assessments and penetration tests focusing on Solr deployments to identify any residual exposure.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain, Poland
CVE-2023-50290: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in Apache Software Foundation Apache Solr
Description
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 the Metrics API.
AI-Powered Analysis
Technical Analysis
CVE-2023-50290 is a vulnerability in Apache Solr versions 9.0.0 up to but not including 9.3.0, classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). The issue arises from the Solr Metrics API, which by default publishes all unprotected environment variables available to each Solr instance. While users can specify environment variables to hide, the default protections only cover known secret Java system properties. Environment variables differ from Java system properties in that they are set at the host level rather than per Java process, making it difficult to strictly define or restrict them within Solr. This results in potentially sensitive environment variables being exposed via the Metrics API. Access to this API requires the "metrics-read" permission, so only users with this permission can exploit the vulnerability. In environments where Solr Cloud is configured with authorization, the risk is limited to users granted this permission. The vulnerability does not require user interaction and can be exploited remotely over the network. The CVSS v3.1 base score is 6.5 (medium severity), reflecting high confidentiality impact but no impact on integrity or availability. The recommended remediation is to upgrade to Apache Solr version 9.3.0 or later, where environment variables are no longer published via the Metrics API, effectively mitigating the issue. No known exploits are currently reported in the wild.
Potential Impact
For European organizations using Apache Solr versions 9.0.0 to before 9.3.0, this vulnerability poses a significant risk of sensitive information leakage. Environment variables often contain credentials, API keys, or configuration details that could facilitate further attacks if disclosed to unauthorized users. Although exploitation requires "metrics-read" permission, insider threats or compromised accounts with this permission could lead to unauthorized data exposure. This could result in loss of confidentiality, regulatory non-compliance (e.g., GDPR violations if personal data is indirectly exposed), and potential reputational damage. Since Solr is widely used in enterprise search and big data applications, exposure of environment variables could aid attackers in lateral movement or privilege escalation within affected organizations. The vulnerability does not affect system integrity or availability directly but undermines trust in system security and confidentiality.
Mitigation Recommendations
1. Upgrade Apache Solr to version 9.3.0 or later immediately, as this version removes environment variable exposure via the Metrics API. 2. Review and restrict the assignment of the "metrics-read" permission to only trusted and necessary users or service accounts. 3. Audit environment variables on hosts running Solr to minimize sensitive data exposure; avoid storing secrets in environment variables where possible. 4. Implement network segmentation and access controls to limit who can reach the Solr Metrics API endpoints. 5. Monitor and log usage of the Metrics API to detect unusual access patterns or unauthorized attempts. 6. Consider additional application-layer encryption or secrets management solutions to reduce reliance on environment variables for sensitive data. 7. Conduct regular security assessments and penetration tests focusing on Solr deployments to identify any residual exposure.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- apache
- Date Reserved
- 2023-12-06T17:35:24.747Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9817c4522896dcbd7322
Added to database: 5/21/2025, 9:08:39 AM
Last enriched: 7/4/2025, 11:41:25 PM
Last updated: 8/12/2025, 12:02:58 AM
Views: 14
Related Threats
CVE-2025-6184: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in themeum Tutor LMS Pro
HighCVE-2025-8762: Improper Physical Access Control in INSTAR 2K+
HighCVE-2025-8761: Denial of Service in INSTAR 2K+
HighCVE-2025-8760: Buffer Overflow in INSTAR 2K+
CriticalCVE-2025-6715: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in LatePoint
CriticalActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.