gitsafehub
github.com/jart/solandra ↗

jart/solandra

scanned 2026-08-14 · git 64e1d19
1 of 6 checks flagged a security issue
🔴 Needs attention
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets✓Vulnerable dependencies18Known OSS vulnerabilities—Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 18 found · 2 serious

Packages you depend on that have known security holes (CVEs).

  • Serious CVE-2015-7501 apache-commons-collections: InvokerTransformer code execution during deserialisation
    pom.xml
    A package you depend on has a known security hole (CVE-2015-7501). Fix: Update that package to its patched version.
  • Serious CVE-2021-44521 cassandra: RCE for scripted UDFs
    pom.xml
    A package you depend on has a known security hole (CVE-2021-44521). Fix: Update that package to its patched version.
  • Worth fixing CVE-2015-6420 Insecure Deserialization in Apache Commons Collection
    pom.xml
    A package you depend on has a known security hole (CVE-2015-6420). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-23015 org.apache.cassandra:cassandra-all: Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions
    pom.xml
    A package you depend on has a known security hole (CVE-2025-23015). Fix: Update that package to its patched version.
  • Worth fixing CVE-2012-6612 Solr: XML eXternal Entity (XXE) flaw in XML and XSLT UpdateRequestHandler
    pom.xml
    A package you depend on has a known security hole (CVE-2012-6612). Fix: Update that package to its patched version.
  • Worth fixing CVE-2017-3163 solr: Directory traversal via Index Replication HTTP API
    pom.xml
    A package you depend on has a known security hole (CVE-2017-3163). Fix: Update that package to its patched version.
  • Worth fixing CVE-2017-3164 Server Side Request Forgery in Apache Solr, versions 1.3 until 7.6 (in ...
    pom.xml
    A package you depend on has a known security hole (CVE-2017-3164). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-1308 Solr: XML external entity expansion in handler/dataimport/DataImporter.java allows remote attackers to read arbitrary files
    pom.xml
    A package you depend on has a known security hole (CVE-2018-1308). Fix: Update that package to its patched version.
  • Worth fixing CVE-2019-0193 solr: Remote Code Execution via DataImportHandler
    pom.xml
    A package you depend on has a known security hole (CVE-2019-0193). Fix: Update that package to its patched version.
  • Worth fixing CVE-2019-12401 solr: XML resource consumption attack via update handler
    pom.xml
    A package you depend on has a known security hole (CVE-2019-12401). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-29262 solr: misapplied Zookeeper ACLs can result in leakage of configured authentication and authorization settings
    pom.xml
    A package you depend on has a known security hole (CVE-2021-29262). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-24814 solr: org.apache.solr: Apache Solr: Core-creation with "trusted" configset can use arbitrary untrusted files
    pom.xml
    A package you depend on has a known security hole (CVE-2025-24814). Fix: Update that package to its patched version.
  • Worth fixing CVE-2013-6397 Solr: directory traversal when loading XSL stylesheets and Velocity templates
    pom.xml
    A package you depend on has a known security hole (CVE-2013-6397). Fix: Update that package to its patched version.
  • Worth fixing CVE-2013-6407 Solr: XML eXternal Entity (XXE) flaw in XML and XSLT UpdateRequestHandler
    pom.xml
    A package you depend on has a known security hole (CVE-2013-6407). Fix: Update that package to its patched version.
  • Worth fixing CVE-2013-6408 Solr: XML eXternal Entity (XXE) flaw in DocumentAnalysisRequestHandler
    pom.xml
    A package you depend on has a known security hole (CVE-2013-6408). Fix: Update that package to its patched version.
  • Worth fixing CVE-2015-8795 Improper Neutralization of Input During Web Page Generation in Apache Solr
    pom.xml
    A package you depend on has a known security hole (CVE-2015-8795). Fix: Update that package to its patched version.
  • Worth fixing CVE-2015-8797 Improper Neutralization of Input During Web Page Generation in Apache Solr
    pom.xml
    A package you depend on has a known security hole (CVE-2015-8797). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-11802 solr: Information disclosure via Rule-base Authorization plugin
    pom.xml
    A package you depend on has a known security hole (CVE-2018-11802). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ timed out

Your dependencies cross-checked against the OSV vulnerability database.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OSV-Scanner v1.9.2 · Apache-2.0

error: timeout after 120s

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ none found ✓

Packages that look intentionally malicious: typosquats, sneaky install scripts.

Nothing found by this check. ✓

via Guarddog v2.10.0 · Apache-2.0

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ didn’t run

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OpenSSF Scorecard · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.