← Back to scan
File as GitHub Issue repo: fortra/impacket

Push this scan report to fortra/impacket

Click 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.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Silent Exception Swallowing

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
HIGH SEC020 [SEC020] Secret Printed to Logs: Debug or diagnostic code appears to print a credential-b… impacket/examples/ldap_shell.py:213
HIGH SEC013 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file pat… examples/ticketConverter.py:106
MED ERR001 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even… impacket/smb3.py:712
MED ERR001 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even… impacket/smbserver.py:4387
MED ERR001 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even… impacket/tds.py:1561
MED SEC014 [SEC014] SSL Verification Disabled: SSL certificate verification is disabled, allowing ma… impacket/examples/__init__.py:18
MED SEC014 [SEC014] SSL Verification Disabled: SSL certificate verification is disabled, allowing ma… impacket/tds.py:1457
MED AUC001 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks… —
MED DKR007 Docker build context has no .dockerignore .dockerignore
MED AIC003 Duplicated implementation block across source files impacket/mqtt.py:159
MED AIC003 Duplicated implementation block across source files impacket/krb5/keytab.py:80
MED AIC003 Duplicated implementation block across source files impacket/dcerpc/v5/tsch.py:23
MED AIC003 Duplicated implementation block across source files impacket/dcerpc/v5/rprn.py:7
MED DKR001 Docker final stage has no non-root USER Dockerfile:10
MED WEB003 Public web service has no security.txt .well-known/security.txt
MED SEC005 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input. impacket/examples/smbclient.py:98
MED SEC005 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input. examples/mimikatz.py:109
MED SEC005 [SEC005] Command Injection Risk: Unsafe shell execution or eval of user input. examples/ntfs-read.py:1259
MED CORE_LARGE_FILES Average file size is 560 lines (recommend <300) —
LOW DKR012 Dockerfile keeps pip download cache Dockerfile:8
LOW DKR012 Dockerfile keeps pip download cache Dockerfile:4
Reset to top 5 21 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `fortra/impacket`

**Score: 71/100 (B+)**  ·  32 findings  ·  scanned 2026-05-15 16:00 UTC  ·  188,093 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 2 |
| MEDIUM | 17 |
| LOW | 2 |

📊 [Full filterable report](https://repobility.com/scan/9034f894-6baa-4d67-938c-5b1fd00c9965/)  ·  ![scorecard](https://repobility.com/scan/9034f894-6baa-4d67-938c-5b1fd00c9965/report.png?v=1778860812-s2)

### Top findings

1. **HIGH** `SEC020` — Secret Printed to Logs
   `impacket/examples/ldap_shell.py:213` · A07:2021 Identification & Authentication Failures
2. **HIGH** `SEC013` — Path Traversal — User Input in File Path
   `examples/ticketConverter.py:106` · A01:2021 Broken Access Control (path traversal)
3. **MEDIUM** `ERR001` — Silent Exception Swallowing
   `impacket/smb3.py:712`
4. **MEDIUM** `ERR001` — Silent Exception Swallowing
   `impacket/smbserver.py:4387`
5. **MEDIUM** `ERR001` — Silent Exception Swallowing
   `impacket/tds.py:1561`

---

**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/9034f894-6baa-4d67-938c-5b1fd00c9965/_
Already filed
This repo publishes a SECURITY.md policy and the scan contains 2 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'fortra/impacket' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
I read the warnings â override Cancel

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.