Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

palo module location fix #1014

Merged
merged 3 commits into from
Feb 17, 2025
Merged

Conversation

securestep9
Copy link
Collaborator

Proposed change

Fix for the incorrect locations in the pushed PR 1013

Type of change

  • New core framework functionality
  • Bugfix (non-breaking change which fixes an issue)
  • Code refactoring without any functionality changes
  • New or existing module/payload change
  • Localization improvement
  • Dependency upgrade
  • Documentation improvement

Checklist

  • I've followed the contributing guidelines
  • I've run make pre-commit, it didn't generate any changes
  • I've run make test, all tests passed locally

…alto_panos_cve_2025_0108.yaml

Fix of the incorrect location for the module

Signed-off-by: Sam Stepanyan <[email protected]>
location fix

Signed-off-by: Sam Stepanyan <[email protected]>
added CVE-2025-0108 module to the docs

Signed-off-by: Sam Stepanyan <[email protected]>
@securestep9 securestep9 added this pull request to the merge queue Feb 17, 2025
Merged via the queue into master with commit 507a098 Feb 17, 2025
17 checks passed
@securestep9 securestep9 deleted the securestep9-palo-module-location-fix branch February 17, 2025 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants