svilgelm/cloudferry

scanned 2026-08-11 · git 4459c0d

1 of 6 checks flagged a security issue

🔴 Needs attention

Only 2 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ⓘ 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 400s

Vulnerable dependencies — Trivyⓘ 18 found · 11 serious

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

Serious CVE-2024-36039 python-pymysql: SQL injection if used with untrusted JSON input

cloudferry_devlab/requirements.txt

A package you depend on has a known security hole (CVE-2024-36039). Fix: Update that package to its patched version.
Serious CVE-2017-18342 PyYAML: yaml.load() API could execute arbitrary code

cloudferry_devlab/requirements.txt

A package you depend on has a known security hole (CVE-2017-18342). Fix: Update that package to its patched version.
Serious CVE-2020-14343 PyYAML: incomplete fix for CVE-2020-1747

cloudferry_devlab/requirements.txt

A package you depend on has a known security hole (CVE-2020-14343). Fix: Update that package to its patched version.
Serious CVE-2019-7164 python-sqlalchemy: SQL Injection when the order_by parameter can be controlled

cloudferry_devlab/requirements.txt

A package you depend on has a known security hole (CVE-2019-7164). Fix: Update that package to its patched version.
Serious CVE-2019-7548 python-sqlalchemy: SQL Injection when the group_by parameter can be controlled

cloudferry_devlab/requirements.txt

A package you depend on has a known security hole (CVE-2019-7548). Fix: Update that package to its patched version.
Serious CVE-2024-36039 python-pymysql: SQL injection if used with untrusted JSON input

requirements.txt

A package you depend on has a known security hole (CVE-2024-36039). Fix: Update that package to its patched version.
Serious CVE-2018-7750 python-paramiko: Authentication bypass in transport.py

requirements.txt

A package you depend on has a known security hole (CVE-2018-7750). Fix: Update that package to its patched version.
Serious CVE-2017-18342 PyYAML: yaml.load() API could execute arbitrary code

requirements.txt

A package you depend on has a known security hole (CVE-2017-18342). Fix: Update that package to its patched version.
Serious CVE-2020-14343 PyYAML: incomplete fix for CVE-2020-1747

requirements.txt

A package you depend on has a known security hole (CVE-2020-14343). Fix: Update that package to its patched version.
Serious CVE-2019-7164 python-sqlalchemy: SQL Injection when the order_by parameter can be controlled

requirements.txt

A package you depend on has a known security hole (CVE-2019-7164). Fix: Update that package to its patched version.
Serious CVE-2019-7548 python-sqlalchemy: SQL Injection when the group_by parameter can be controlled

requirements.txt

A package you depend on has a known security hole (CVE-2019-7548). Fix: Update that package to its patched version.
Worth fixing CVE-2018-17175 In the marshmallow library before 2.15.1 and 3.x before 3.0.0b9 for Py ...

requirements.txt

A package you depend on has a known security hole (CVE-2018-17175). Fix: Update that package to its patched version.
Worth fixing CVE-2018-1000805 python-paramiko: Authentication bypass in auth_handler.py

requirements.txt

A package you depend on has a known security hole (CVE-2018-1000805). Fix: Update that package to its patched version.
Worth fixing CVE-2018-1000807 pyOpenSSL: Use-after-free in X509 object handling

requirements.txt

A package you depend on has a known security hole (CVE-2018-1000807). Fix: Update that package to its patched version.
Worth fixing CVE-2018-1000808 pyOpenSSL: Failure to release memory before removing last reference in PKCS #12 Store

requirements.txt

A package you depend on has a known security hole (CVE-2018-1000808). Fix: Update that package to its patched version.
Worth fixing CVE-2013-6418 pywbem: TOCTOU vulnerability in certificate validation

requirements.txt

A package you depend on has a known security hole (CVE-2013-6418). Fix: Update that package to its patched version.
Worth fixing CVE-2013-6444 pywbem: failure to check certificate hostname

requirements.txt

A package you depend on has a known security hole (CVE-2013-6444). Fix: Update that package to its patched version.
Minor CVE-2026-27448 pyOpenSSL: TLS connection bypass via unhandled callback exception in set_tlsext_servername_callback

requirements.txt

A package you depend on has a known security hole (CVE-2026-27448). 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 400s

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ⓘ timed out

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

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

via Guarddog v2.10.0 · Apache-2.0

error: pypi:timeout

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.