v1.1.3

What's Changed

• Fix schema parse error by @RamanaReddy0M in #98
• Update executable version to 1.1.3 by @RamanaReddy0M in #99

New Contributors

• @RamanaReddy0M made their first contribution in #98

Full Changelog: v1.1.2...v1.1.3

v1.1.2

What's Changed

• Replace deprecated requests protocol name with http by @princechaddha in #77
• Add support for the negative attribute by @dogancanbakir in #78

Dependency updates:

• rsyntaxtextarea from 3.3.0 to 3.3.4
• autocomplete from 3.3.0 to 3.3.1
• gson from 2.10 to 2.10.1

Dev dependency updates:

• annotations from 23.1.0 to 24.0.1
• org.junit.jupiter:junit-jupiter from 5.9.1 to 5.10.0
• org.apache.maven.plugins:maven-surefire-plugin from 2.22.2 to 3.2.1

New Contributors

• @princechaddha made their first contribution in #77
• @dogancanbakir made their first contribution in #78

Full Changelog: v1.1.1...v1.1.2

v1.1.1

What's Changed

• Fixed a bug on windows with path not correctly updating after saving by @forgedhallpass in #53

Full Changelog: v1.1.0...v1.1.1

v1.1.0

New features

• Add Tab support for the template generator window
• Adding selected multi-request support from History tab
• "Add to" content to generated templates
• Auto-complete classification information based on CVE id
• Add CLI flag helper

Bug fixes

• NPE when the JSON schema cannot be downloaded
• Try to read the nuclei JSON schema from the disk as a fallback
• Mismatched indentation

Improvements

• Better and more detailed logging
• Persist modified font sizes between sessions
• Architecture refactoring
• Misc UI and UX improvements

Version updates

• GSON 2.8.9 -> 2.9.0
• maven-compiler-plugin 3.8.1 -> 3.10.1
• maven-assembly-plugin 3.3.0 -> 3.4.0
• maven-release-plugin 3.0.0-M1 -> 3.0.0-M6
• snake-yaml 1.29 -> 1.30
• rsyntaxtextarea 3.1.6 -> 3.2.0
• autocomplete 3.1.5 -> 3.2.0

Full Changelog: v1.0.0-rc1...v1.1.0

v1.1.0-beta

This is an early access release containing new features and a lot of enhancements. The complete release notes will be shared within the v1.1.0 release.

v1.0.0-rc1

Features

Template matcher generation

• Word and Binary matcher creation using selected response snippets from Proxy history or Repeater contexts
• Multi-line selections are split to separate words for readability
• Binary matchers are created for selections containing non-ASCII characters
• The part field is auto-set based on whether the selection was in the request header or body
• Every generated template auto-includes a Status matcher, using the HTTP status code of the response

Request template generation

• In the Intruder tab, selected payload positions can be used to generate request templates, using one of the following attack types: Battering ram, Pitchfork or Cluster bomb
• The selected text snippet from an HTTP request under the Proxy or Repeater tab can be used to generate a request template with the attack type defaulting to Battering ram

Template execution

• Generated templates can be executed instantly, and the output is shown in the same window for convenience
• The plugin auto-generates the CLI command, using the absolute nuclei path, absolute template path and target information extracted from the desired request
• History of unique, executed commands are stored, can be quick searched and re-executed within the current session

Experimental features

• (Non-contextual) YAML property and value auto-complete, using reserved words from the nuclei JSON schema
• Syntax highlighting of YAML properties, based on reserved words

Productivity

• Almost every action can be triggered using keyboard shortcuts:
  • F1: open nuclei template documentation
  • Ctrl + Enter: execute current template
  • Ctrl + Shift + E: jump to the template editor
  • Ctrl + L: jump to the CLI input field
  • Ctrl + S: save the current template
  • Ctrl + Plus/Minus: increase/decrease font size
  • Ctrl + Q: quit
• The template path is auto-updated if the template is saved to a new location
• The template-id is recommended as file name when saving

Settings

• The plugin attempts to auto-detect and complete the configuration values
• The code searches for the nuclei binary path, using the values from the process's environmental PATH variable.
  Note: the BurpSuite binary, opposed to the stand-alone BurpSuite jar, might not have access to
  the current users's PATH variable.
• The target template path is calculated based on the default nuclei template directory, configured under <USER_HOME>/.config/nuclei/.templates-config.json
• The name of the currently logged-in operating system user is used as a default value for the template author configuration

Look and feel

• The template generator window supports Dark and Light themes. The presented theme is chosen based on the selected BurpSuite theme, under User Options
• Support for colored nuclei output
• Modifiable font size in the template editor and command output