hydra-gate-unsafe-auth-resolver

Detect PHP authorization methods that return null after catching Throwable exceptions.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ConductionNL/shillinq --skill hydra-gate-unsafe-auth-resolver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hydra-gate-unsafe-auth-resolver
Source: https://github.com/ConductionNL/shillinq/tree/main/.claude/skills/hydra-gate-unsafe-auth-resolver
Command: npx skills add https://github.com/ConductionNL/shillinq --skill hydra-gate-unsafe-auth-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents security vulnerabilities where authorization checks are silently skipped due to improper error handling in service methods, specifically when catching exceptions and returning null.

Core Features & Use Cases

  • Vulnerability Detection: Scans PHP service and controller methods for the fail-open pattern where Throwable exceptions are caught and null is returned.
  • Security Hardening: Provides clear remediation paths to ensure authorization subsystems fail closed rather than allowing unauthorized access.
  • Use Case: Use this tool during code reviews or CI pipelines to identify and fix instances where a missing authorization service might allow an unauthenticated user to bypass role checks.

Quick Start

Run the hydra-gate-unsafe-auth-resolver skill to scan the current repository for unsafe authorization resolution patterns.

Frequently Asked Questions about hydra-gate-unsafe-auth-resolver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect silent authentication bypass vulnerabilities in PHP?

To detect silent authentication bypass vulnerabilities in PHP, scan service and controller methods using static analysis to find code where caught Throwable exceptions result in a null return value, bypassing role checks.

Why does catching exceptions and returning null cause an auth bypass?

Catching exceptions and returning null creates a fail-open authorization bypass because the null value skips role validation, allowing unauthenticated users to access protected resources without triggering an error.

How do I prevent fail-open security issues in Nextcloud app controllers?

Prevent fail-open security issues in Nextcloud app controllers by enforcing fail-closed logic during static analysis, ensuring authorization services throw exceptions instead of returning null when failures occur.

Can I use static analysis to scan for unsafe authorization resolvers in my CI pipeline?

You can use static analysis to scan for unsafe authorization resolvers in your CI pipeline by analyzing method bodies to identify Throwable suppression combined with null returns, providing clear remediation paths for code reviews.

What is a fail-closed authorization pattern in PHP service methods?

A fail-closed authorization pattern in PHP service methods ensures that when an authorization service encounters an error or missing dependency, access is explicitly denied rather than returning null and silently allowing unauthenticated access.

Do I need specific dependencies to run static analysis for auth bypass detection?

No specific dependencies are required to run static analysis for auth bypass detection; the skill directly analyzes PHP service and controller method bodies to identify the combination of Throwable suppression and null return values.