Skip to content

Releases: mohamedmoatazsec/SecureScope

Release list

SecureScope 2.0.1

SecureScope 2.0.1 Latest
Latest

Choose a tag to compare

View all tags
@mohamedmoatazsec mohamedmoatazsec released this 18 Oct 05:36
v2.0.1
1b9ec69
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A hardening release from reviewing the scanner's own attack surface: everything a hostile target can send is treated as data in every output, and the scanner cannot be steered or exhausted by the site it is scanning.

Security

  • Console output could be crashed or styled by a hostile header (Server: [/]); all target-derived text is now escaped
  • CSV formula injection neutralised (cells starting with = + - @ are quote-prefixed)
  • Markdown output HTML-escapes target text; evidence stays inside code spans
  • Redirects followed by hand, max 5 hops; a public target can no longer redirect the scanner into loopback/link-local/private address space
  • Response bodies capped at 2 MB, evidence values at 1000 characters
  • GitHub Action inputs passed via environment variables
  • CodeQL (security-extended) and Dependabot enabled

Added

  • target check: redirect chain facts, REDIRECT-HTTPS-TO-HTTP (medium), TARGET-REDIRECTED / RESPONSE-BODY-TRUNCATED (info), REDIRECT-TO-INTERNAL-ADDRESS (low)

Fixed

  • CORS-NO-VARY-ORIGIN only when the origin is reflected
  • Clear error for malformed --baseline files

Full notes: CHANGELOG.md · pip install -U securescope

What's Changed

Full Changelog: v2.0.0...v2.0.1

Contributors

mohamedmoatazsec
Assets 4
Loading

SecureScope 2.0.0

SecureScope 2.0.0

Choose a tag to compare

View all tags
@mohamedmoatazsec mohamedmoatazsec released this 18 Oct 05:00
v2.0.0
791fb0a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

SecureScope 2.0 is a rewrite around evidence-backed findings: every issue has a stable id, severity, confidence, the exact value observed, a remediation and references, and each target gets an A+ to F grade.

Highlights

  • Content-Security-Policy evaluator (unsafe-inline/eval, wildcard and scheme sources, missing object-src/base-uri/form-action, report-only, duplicates; 'strict-dynamic' understood)
  • Header quality: HSTS max-age/includeSubDomains, X-Frame-Options values, frame-ancestors wildcards, Referrer-Policy, Permissions-Policy, COOP, legacy X-XSS-Protection, public caching of HTML
  • Cookies from raw Set-Cookie: Secure/HttpOnly/SameSite, SameSite=None without Secure, __Host-/__Secure- prefix rules, domain scope
  • TLS: validation errors, expiry windows, TLS 1.0/1.1 acceptance, TLS 1.3 support, http→https redirect
  • CORS probes, OPTIONS/TRACE-only method review, version disclosure, security.txt
  • SARIF 2.1.0 for GitHub code scanning, Markdown, redesigned HTML report, JSON with schema, CSV
  • CI gate: --fail-on, --baseline (only new findings fail), --stdout; GitHub Action uses: mohamedmoatazsec/SecureScope@v2; Docker image on GHCR
  • Engagement ergonomics: --proxy (Burp), -H, --cookie, --insecure, targets file, check selection

Breaking changes: ports/subdomains/WHOIS are opt-in; report formats via -f; the methods check no longer sends PUT/DELETE/PATCH; python-whois is an optional extra; new Python API.

Full notes: CHANGELOG.md

Install: pip install git+https://github.com/mohamedmoatazsec/SecureScope.git@v2.0.0 or docker run --rm ghcr.io/mohamedmoatazsec/securescope:2.0.0 example.com

What's Changed

  • SecureScope 2.0: evidence-backed findings, CSP/TLS/cookie analysis, SARIF and CI gating by @mohamedmoatazsec in #2
  • Release 1.1.0: report HTML-injection fix, real CORS analysis, packaging, tests, CI by @mohamedmoatazsec in #1

New Contributors

Full Changelog: https://github.com/mohamedmoatazsec/SecureScope/commits/v2.0.0

Contributors

mohamedmoatazsec
Loading