[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462717#comment-17462717
]
Jon Bristow commented on LOG4J2-3230:
-------------------------------------
This is a different bug to the JNDI one. It is related to the new CVE mentioned
by the 2.17.0. Please do not view this ticket or my sample code as the ONLY way
to trigger the infinite recursion bug. My example was provided only as a way to
provoke others into helping me understand the potential abuse cases (especially
the ones I don’t see immediately!)
please refer to the 2.17 release notes for recommended remediation steps, as I
do not think that my example covers all of the edge cases potentially at play
with this bug.
> Certain strings can cause infinite recursion
> --------------------------------------------
>
> Key: LOG4J2-3230
> URL: https://issues.apache.org/jira/browse/LOG4J2-3230
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.8, 2.8.1, 2.8.2, 2.9.0, 2.9.1, 2.10.0, 2.11.0, 2.11.1,
> 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.13.1, 2.13.2, 2.14.0, 2.13.3, 2.14.1,
> 2.15.0, 2.16.0
> Reporter: Ross Cohen
> Assignee: Carter Kozak
> Priority: Major
> Fix For: 2.17.0
>
> Attachments: sample.tar.gz
>
>
> If a string substitution is attempted for any reason on the following string,
> it will trigger an infinite recursion, and the application will crash:
> ${${::\-${::\-$${::\-j}}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
