3 ms·
See the description here for the rationale why JNDI support was added: https://issues.apache.org/jira/plugins/servlet/mobile#issue/LOG4J2-313 https://issues.apa
by layer8 5y ago
See the description here for the rationale why JNDI support was added: https://issues.apache.org/jira/plugins/servlet/mobile#issue/LOG4J2-313 https://issues.apache.org/jira/plugins/servlet/mobile#issue/...
Nobody there seemed to be aware that the log message text itself is also subject to lookup syntax interpretation and that this would be dangerous given that JNDI also allows remote code-base download and execution from the specified URL.
- Fabricio20 5y agoExcept this particular issue has nothing to do with LDAP! It's perfectly reproducible with RMI for example, another JNDI supported protocol. So much so that the initial RC1 patch was an IF for LDAP, and it was obviously bypassed in seconds.
- layer8 5y agoYou are right, I edited my comment now.
- Sohcahtoa82 5y agoThat page requires a login.
- layer8 5y agoOnly intermittently, try reloading the page.
- jasode 5y agoWhat info does your link provide that the other canonical url for "LOG4J2-313" does not? The url people usually copy&paste that doesn't require a login is: https://issues.apache.org/jira/browse/LOG4J2-313 https://issues.apache.org/jira/browse/LOG4J2-313
- layer8 5y agoIt seems my link is the mobile version. I'm currently on mobile, that's why. I can't edit the original comment anymore unfortunately.