gitsafehub
github.com/asutosh936/hazelcast-code-samples ↗

asutosh936/hazelcast-code-samples

scanned 2026-08-11 · git 192954d
1 of 6 checks flagged a security issue
🔴 Needs attention
Only 3 of 6 checks finished — treat this as provisional. Re-check ↻

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

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

Security checks

Leaked secrets — Gitleaksⓘ timed out

API keys, passwords or tokens committed into the repo.

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

via Gitleaks v8.21.2 · MIT

error: timeout after 120s

Vulnerable dependencies — Trivyⓘ 435 found · 64 serious

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

  • Serious CVE-2022-41853 hsqldb: Untrusted input may lead to RCE attack
    distributed-map/mapstore/pom.xml
    A package you depend on has a known security hole (CVE-2022-41853). Fix: Update that package to its patched version.
  • Serious CVE-2022-41853 hsqldb: Untrusted input may lead to RCE attack
    distributed-map/pom.xml
    A package you depend on has a known security hole (CVE-2022-41853). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    enterprise/hd-memory-client-server/hd-memory-examples-client/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    enterprise/hd-memory-client-server/hd-memory-examples-server/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    enterprise/hd-memory-client-server/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    enterprise/hd-memory-client-server/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    enterprise/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    enterprise/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    hazelcast-integration/hibernate-2ndlevel-cache/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2015-1832 Derby: XXE attack possible by using XmlVTI and the XML datatype
    hazelcast-integration/hibernate-2ndlevel-cache/pom.xml
    A package you depend on has a known security hole (CVE-2015-1832). Fix: Update that package to its patched version.
  • Serious CVE-2022-46337 A cleverly devised username might bypass LDAP authentication checks. I ...
    hazelcast-integration/hibernate-2ndlevel-cache/pom.xml
    A package you depend on has a known security hole (CVE-2022-46337). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    hazelcast-integration/hibernate-jpa-2ndlevel-cache/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2015-7501 apache-commons-collections: InvokerTransformer code execution during deserialisation
    hazelcast-integration/hibernate-jpa-2ndlevel-cache/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-2015-1832 Derby: XXE attack possible by using XmlVTI and the XML datatype
    hazelcast-integration/hibernate-jpa-2ndlevel-cache/pom.xml
    A package you depend on has a known security hole (CVE-2015-1832). Fix: Update that package to its patched version.
  • Serious CVE-2022-46337 A cleverly devised username might bypass LDAP authentication checks. I ...
    hazelcast-integration/hibernate-jpa-2ndlevel-cache/pom.xml
    A package you depend on has a known security hole (CVE-2022-46337). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2022-36437 hazelcast: Hazelcast connection caching
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2022-36437). Fix: Update that package to its patched version.
  • Serious CVE-2015-1832 Derby: XXE attack possible by using XmlVTI and the XML datatype
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2015-1832). Fix: Update that package to its patched version.
  • Serious CVE-2022-46337 A cleverly devised username might bypass LDAP authentication checks. I ...
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2022-46337). Fix: Update that package to its patched version.
  • Serious CVE-2015-1832 Derby: XXE attack possible by using XmlVTI and the XML datatype
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2015-1832). Fix: Update that package to its patched version.
  • Serious CVE-2022-46337 A cleverly devised username might bypass LDAP authentication checks. I ...
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2022-46337). Fix: Update that package to its patched version.
  • Serious CVE-2015-1832 Derby: XXE attack possible by using XmlVTI and the XML datatype
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2015-1832). Fix: Update that package to its patched version.
  • Serious CVE-2022-46337 A cleverly devised username might bypass LDAP authentication checks. I ...
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2022-46337). Fix: Update that package to its patched version.
  • Serious CVE-2022-22978 springframework: Authorization Bypass in RegexRequestMatcher
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2022-22978). Fix: Update that package to its patched version.
  • Serious CVE-2024-38821 Spring-WebFlux: Authorization Bypass of Static Resources in WebFlux Applications
    hazelcast-integration/pom.xml
    A package you depend on has a known security hole (CVE-2024-38821). Fix: Update that package to its patched version.
… 410 more not shown

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.