70a43fda8b
Blocks .env, *.key, *.pem, id_rsa*, secrets.*, credentials.json, etc. Preventive — no exposure found; future commits can't accidentally leak these. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
CVE Resolution Tool for NinjaOne
Queries NinjaOne's REST API to aggregate CVE/vulnerability data across all organizations and prioritize remediation efforts.
Setup
-
Copy config example and add your NinjaOne API credentials:
cp config.example.py config.py -
Get API credentials from NinjaOne:
- Go to Administration > Apps > API
- Create a new API application (Client Credentials grant type)
- Copy the Client ID and Client Secret
-
Install dependencies:
pip install -r requirements.txt
Usage
python ninjaone.py
NinjaOne API Endpoints Used
| Endpoint | Description |
|---|---|
GET /api/v2/organizations |
List all organizations |
GET /api/v2/devices-detailed |
List all devices with details |
GET /api/v2/device/{id}/software |
Device software inventory |
GET /api/v2/queries/os-patches |
OS patches report |
GET /api/v2/queries/software-patches |
Third-party software patches |
GET /api/v2/vulnerability/scan-groups |
Vulnerability scan data |
Output
Generates a prioritized CVE remediation report showing:
- Summary across all organizations
- Patches grouped by CVSS severity (Critical/High/Medium/Low)
- Critical items requiring immediate attention
- Affected device counts