Skip to content

zaproxy contains log4j exploit code #599

Open
Open
zaproxy contains log4j exploit code#599

Description

@BustedSec
BustedSec
opened on Sep 20, 2022

2022-09-20 06_23_49-Window
The version of ZAP installed is behind the master branch that addressed this

References:
https://www.blumira.com/analysis-log4shell-local-trigger/
https://www.lunasec.io/docs/blog/log4j-zero-day-update-on-cve-2021-45046/

zaproxy/zaproxy#6979.
zaproxy/zaproxy#6980

Unsure what magic was done,
image
but the magic needs updating to the most recent URL to pull a newer version via wget.

Activity

  1. 0xv1n commented on Sep 28, 2024

    @0xv1n
    0xv1n
    on Sep 28, 2024
    Contributor

    Old issue, but no longer needs to be addressed as the latest Zaproxy release uses log4j 2.20.0 per bom.json .

    ref: https://github.com/zaproxy/zaproxy/releases/tag/v2.15.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions