gitsafehub
github.com/lostb1t/crowdsec-bouncer-traefik-plugin ↗

lostb1t/crowdsec-bouncer-traefik-plugin

scanned 2026-08-12 · git 7d38d18
1 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets47Vulnerable dependencies✓Known OSS vulnerabilities✓Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ 47 found · 1 serious

API keys, passwords or tokens committed into the repo.

  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    README.md:187
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    examples/custom-ban-page/docker-compose.yml:43
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    examples/custom-ban-page/docker-compose.yml:55
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    docker-compose.yml:53
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    docker-compose.local.yml:50
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    examples/standalone-mode/docker-compose.alone.yml:39
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    examples/appsec-enabled/docker-compose.appsec-enabled.yml:44
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    examples/appsec-enabled/docker-compose.appsec-enabled.yml:60
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    docker-compose.local.yml:39
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    docker-compose.local.yml:52
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    docker-compose.local.yml:61
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    examples/captcha/docker-compose.captcha.yml:43
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    examples/captcha/docker-compose.captcha.yml:64
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    docker-compose.yml:42
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    docker-compose.yml:61
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    docker-compose.yml:73
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    exemples/behind-proxy/docker-compose.cloudflare.yml:62
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    exemples/behind-proxy/docker-compose.cloudflare.yml:81
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    exemples/behind-proxy/docker-compose.cloudflare.yml:94
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    exemples/trusted-ips/docker-compose.trusted.yml:44
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    exemples/trusted-ips/docker-compose.trusted.yml:63
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    exemples/trusted-ips/docker-compose.trusted.yml:76
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    exemples/redis-cache/docker-compose.redis.yml:47
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    exemples/redis-cache/docker-compose.redis.yml:67
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    exemples/redis-cache/docker-compose.redis.yml:82
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
… 22 more not shown

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ none found ✓

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

Nothing found by this check. ✓

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 45 found

Your dependencies cross-checked against the OSV vulnerability database.

  • FYI GO-2025-3503 HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-22870). Fix: Update that package to its patched version.
  • FYI GO-2025-3563 Request smuggling due to acceptance of invalid chunked data in net/http
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-22871). Fix: Update that package to its patched version.
  • FYI GO-2025-3750 Inconsistent handling of O_CREATE|O_EXCL on Unix and Windows in os in syscall
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-0913). Fix: Update that package to its patched version.
  • FYI GO-2025-3751 Sensitive headers not cleared on cross-origin redirect in net/http
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-4673). Fix: Update that package to its patched version.
  • FYI GO-2025-3849 Incorrect results returned from Rows.Scan in database/sql
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-47907). Fix: Update that package to its patched version.
  • FYI GO-2025-3956 Unexpected paths returned from LookPath in os/exec
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-47906). Fix: Update that package to its patched version.
  • FYI GO-2025-4006 Excessive CPU consumption in ParseAddress in net/mail
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-61725). Fix: Update that package to its patched version.
  • FYI GO-2025-4007 Quadratic complexity when checking name constraints in crypto/x509
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-58187). Fix: Update that package to its patched version.
  • FYI GO-2025-4008 ALPN negotiation error contains attacker controlled information in crypto/tls
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-58189). Fix: Update that package to its patched version.
  • FYI GO-2025-4009 Quadratic complexity when parsing some invalid inputs in encoding/pem
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-61723). Fix: Update that package to its patched version.
  • FYI GO-2025-4010 Insufficient validation of bracketed IPv6 hostnames in net/url
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-47912). Fix: Update that package to its patched version.
  • FYI GO-2025-4011 Parsing DER payload can cause memory exhaustion in encoding/asn1
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-58185). Fix: Update that package to its patched version.
  • FYI GO-2025-4012 Lack of limit when parsing cookies can cause memory exhaustion in net/http
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-58186). Fix: Update that package to its patched version.
  • FYI GO-2025-4013 Panic when validating certificates with DSA public keys in crypto/x509
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-58188). Fix: Update that package to its patched version.
  • FYI GO-2025-4014 Unbounded allocation when parsing GNU sparse map in archive/tar
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-58183). Fix: Update that package to its patched version.
  • FYI GO-2025-4015 Excessive CPU consumption in Reader.ReadResponse in net/textproto
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-61724). Fix: Update that package to its patched version.
  • FYI GO-2025-4155 Excessive resource consumption when printing error string for host certificate validation in crypto/x509
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-61729). Fix: Update that package to its patched version.
  • FYI GO-2025-4175 Improper application of excluded DNS name constraints when verifying wildcard names in crypto/x509
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-61727). Fix: Update that package to its patched version.
  • FYI GO-2026-4337 Unexpected session resumption in crypto/tls
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-68121). Fix: Update that package to its patched version.
  • FYI GO-2026-4340 Handshake messages may be processed at the incorrect encryption level in crypto/tls
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-61730). Fix: Update that package to its patched version.
  • FYI GO-2026-4341 Memory exhaustion in query parameter parsing in net/url
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-61726). Fix: Update that package to its patched version.
  • FYI GO-2026-4342 Excessive CPU consumption when building archive index in archive/zip
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-61728). Fix: Update that package to its patched version.
  • FYI GO-2026-4403 Improper access to parent directory of root in os
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2025-22873). Fix: Update that package to its patched version.
  • FYI GO-2026-4601 Incorrect parsing of IPv6 host literals in net/url
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2026-25679). Fix: Update that package to its patched version.
  • FYI GO-2026-4602 FileInfo can escape from a Root in os
    /workdirs/scan-9be6fc9f-3746-402a-b9b5-1d5fe510ebdc/go.mod
    A package you depend on has a known security hole (CVE-2026-27139). Fix: Update that package to its patched version.
… 20 more not shown

via OSV-Scanner v1.9.2 · Apache-2.0

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.