t8y2/dbx
t8y2/dbxClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Server-Side Request Forgery (SSRF) — outbound HTTP from user input
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `t8y2/dbx` **Score: 70/100 (B)** · 37 findings · scanned 2026-05-16 22:31 UTC · 80,578 LOC | Severity | Count | |---|---| | CRITICAL | 2 | | HIGH | 4 | | MEDIUM | 9 | | LOW | 22 | 📊 [Full filterable report](https://repobility.com/scan/446a5605-265f-4dce-86ba-d4c30af53d8e/) ·  ### Top findings 1. **CRITICAL** `SEC022` — Database URL With Embedded Credential `crates/dbx-core/src/models/connection.rs:298` · A07:2021 Identification & Authentication Failures 2. **CRITICAL** `SEC022` — Database URL With Embedded Credential `crates/dbx-core/src/connection_secrets.rs:393` · A07:2021 Identification & Authentication Failures 3. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `crates/dbx-core/src/db/mysql.rs:171` · A10:2021 SSRF 4. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `crates/dbx-core/src/db/elasticsearch_driver.rs:28` · A10:2021 SSRF 5. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `crates/dbx-core/src/db/clickhouse_driver.rs:57` · A10:2021 SSRF --- **Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately. --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/446a5605-265f-4dce-86ba-d4c30af53d8e/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.