← Scan another repo

github.com/syncthing/syncthing

@ 946e2b83a1f6

Submitted 8/4/2026, 10:25:55 AM · Status: ok

Risk grade
F
100 / 100
Findings
122
0 critical29 high44 medium5 low44 info0 on CISA KEV0ATT&CK
Showing 122 of 122 findings

Findings

  • Detected generic-api-key: Detected a Generic API Key, potentially exposing access to various services and sensitive operations
    Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    gitleaks
  • Detected generic-api-key: Detected a Generic API Key, potentially exposing access to various services and sensitive operations
    Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    gitleaks
  • Detected generic-api-key: Detected a Generic API Key, potentially exposing access to various services and sensitive operations
    Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Detected private-key: Identified a Private Key, which may compromise cryptographic security and sensitive data encryption
    Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    gitleaks
  • Command injection: exec.Command/exec.CommandContext is invoked with a shell (sh/bash -c) plus an interpolated string, or with argv[0] AND its args spread from the same parsed slice (words[0], words[1:
    Command injection: exec.Command/exec.CommandContext is invoked with a shell (sh/bash -c) plus an interpolated string, or with argv[0] AND its args spread from the same parsed slice (words[0], words[1:]...) — i.e. a command string split into an argv and executed, which lets input …
    semgreplib/versioner/external.go:156
  • Committed PEM private-key material (a "-----BEGIN ... PRIVATE KEY-----" block). Anyone with repo read access holds the key: rotate it, remove it from history, and load keys at runtime from a secret st
    Committed PEM private-key material (a "-----BEGIN ... PRIVATE KEY-----" block). Anyone with repo read access holds the key: rotate it, remove it from history, and load keys at runtime from a secret store / mounted volume instead. (First-party socbox rule; Apache-2.0.)
    semgreplib/api/testdata/config/key.pem:1
  • Committed PEM private-key material (a "-----BEGIN ... PRIVATE KEY-----" block). Anyone with repo read access holds the key: rotate it, remove it from history, and load keys at runtime from a secret st
    Committed PEM private-key material (a "-----BEGIN ... PRIVATE KEY-----" block). Anyone with repo read access holds the key: rotate it, remove it from history, and load keys at runtime from a secret store / mounted volume instead. (First-party socbox rule; Apache-2.0.)
    semgreplib/api/testdata/config/https-key.pem:1
  • SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Us
    SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Use parameterized placeholders ($1/?) with separate args, never string building. C…
    semgrepinternal/db/sqlite/folderdb_update.go:628
  • SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Us
    SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Use parameterized placeholders ($1/?) with separate args, never string building. C…
    semgrepinternal/db/sqlite/db_service.go:301
  • SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Us
    SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Use parameterized placeholders ($1/?) with separate args, never string building. C…
    semgrepinternal/db/sqlite/db_folderdb.go:77
  • SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Us
    SQL built by concatenation/Sprintf passed to Query/Exec/QueryRow — SQL injection. The statement text is assembled from a formatted or concatenated string (directly or via an intermediate variable). Use parameterized placeholders ($1/?) with separate args, never string building. C…
    semgrepinternal/db/sqlite/basedb.go:69
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivyDockerfile:0
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivyDockerfile.builder:0
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivyDockerfile.stcrashreceiver:0
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivyDockerfile.stdiscosrv:0
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivyDockerfile.strelaypoolsrv:0
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivyDockerfile.strelaysrv:0
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivyDockerfile.stupgrades:0
  • Image user should not be 'root'
    Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.
    trivyDockerfile.ursrv:0

This report is public.