first commit

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,22 @@
+---
+name: Bug Report
+about: Report a bug or unexpected behavior in Exposor
+title: "[Bug] <Short description of the bug>"
+labels: bug
+assignees: ''
+
+---
+
+## Describe the Bug
+A clear and concise description of what the bug is.
+
+## Steps to Reproduce
+1. Go to '...'
+2. Run the command '...'
+3. Use the YAML file '...'
+4. See the error '...'
+
+## Expected Behavior
+A clear and concise description of what you expected to happen.
+
+## Logs/Output

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature Request
+about: Suggest a new feature or improvement for Exposor
+title: "[Feature] <Short description of the feature>"
+labels: enhancement
+assignees: ''
+
+---
+
+## Feature Description
+A clear and concise description of the feature you’d like to see.
+
+## Problem Statement
+Explain the problem this feature would solve or the use case it addresses.
+
+## Proposed Solution
+Describe how the feature might be implemented.
+
+## Additional Context
+Add any other context, mockups, or references here.
+
+## Priority Level
+- [ ] High
+- [ ] Medium
+- [ ] Low

.github/ISSUE_TEMPLATE/yaml_request.md

@@ -0,0 +1,28 @@
+---
+name: Technology Detection YAML Request
+about: Request a new YAML file for detecting a specific technology
+title: "[YAML Request] <Vendor/Product Name>"
+labels: yaml
+assignees: ''
+
+---
+
+## Technology Information
+- **cpe**: [e.g. cpe:2.3:a:apache:activemq]
+
+## Purpose of the Detection
+Describe the purpose of this YAML file (e.g., to detect specific technologies or products).
+
+## Detection Queries
+Provide relevant queries for detecting the technology across different platforms:
+```yaml
+shodan: '<query>'
+fofa: '<query>'
+zoomeye: '<query>'
+censys: '<query>'
+```
+
+## Additional Context
+Provide any additional context, documentation, or references to help create the YAML file.
+
+---

.github/workflows/calculate_intels_checksum.yml

@@ -0,0 +1,26 @@
+name: Calculate Folder Checksum
+
+on:
+  push:
+    paths:
+      - 'exposor/intels/**'  # Trigger only when changes occur in the intels folder
+
+jobs:
+  calculate-checksum:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v3
+
+      - name: Calculate Checksum of intels Folder
+        run: |
+          # Ensure the intels directory exists
+          if [ -d "exposor/intels" ]; then
+            # Find all files in the intels folder, sort them, and compute a checksum
+            CHECKSUM=$(find exposor/intels -type f -exec sha256sum {} + | sort | sha256sum | awk '{print $1}')
+            echo "Checksum of intels folder: $CHECKSUM"
+          else
+            echo "intels folder does not exist."
+            exit 1
+          fi

.github/workflows/run_auto_cve.yml

@@ -0,0 +1,53 @@
+name: Print Hello for Changed Files
+
+on:
+  push:
+    paths:
+      - 'exposor/intels/technology_intels/**'  # Trigger on changes in this folder
+
+jobs:
+  print-hello-world:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v3
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          fetch-depth: 0
+
+      - name: Get Changed Files
+        id: get-files
+        run: |
+          # Get the list of changed files in the technology_intels directory
+          CHANGED_FILES=$(git diff --name-only "${{ github.event.before }}" "${{ github.sha }}" | grep "^exposor/intels/technology_intels/")
+          
+          if [ -z "$CHANGED_FILES" ]; then
+            echo "No changed files found in exposor/intels/technology_intels."
+            exit 0
+          fi
+
+          # Export the list of changed files as an output variable
+          echo "changed_files<<EOF" >> $GITHUB_ENV
+          echo "$CHANGED_FILES" >> $GITHUB_ENV
+          echo "EOF" >> $GITHUB_ENV
+
+      - name: Print Hello World for Each File
+        run: |
+          echo "Changed files:"
+          echo "${{ env.changed_files }}"
+          
+          # Loop through each file
+          while IFS= read -r FILE; do
+            echo "Hello, world! File: $FILE"
+          done <<< "${{ env.changed_files }}"
+
+      - name: Run Vulners API Script for Each File
+        run: |
+          echo "Processing changed files with Vulners API:"
+          
+          # Loop through each file and pass it as an argument to vulners-api.py
+          while IFS= read -r FILE; do
+            echo "Running Vulners API for file: $FILE"
+            python3 $GITHUB_WORKSPACE/scripts/vulners-api.py "$FILE"
+          done <<< "${{ env.changed_files }}"

.gitignore

@@ -0,0 +1,171 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.env.example
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# macOS specific
+.DS_Store
+
+# PyCharm
+.idea/
+*.iml
+*.iws
+
+# Visual Studio Code
+.vscode/
+
+#linter
+.flake8
+.trunk