- Creation
- Validation
- Communication & fix
- Disclosure
Mimecast / Server vulnerable to Log4J CVE-2021-44228
BloodyShell
reported 2021-12-11
Server vulnerable to Log4J CVE-2021-44228. The reply originated from a backend server, the originating frontend server has been included in the report for reference.
It is critical to patch log4j or the application using since the issues is exploited in the wild and leads to RCE.
- https://www.lunasec.io/docs/blog/log4j-zero-day/
- https://issues.apache.org/jira/browse/LOG4J2-2109
- https://logging.apache.org/log4j/2.x/security.html
IP:
195.130.217.63Port:
443Detected protocol:
httpsVulnerable URL:
https://195.130.217.63Received reply after a Log4j payload from this host
Orignal request was to 195.130.217.184
Orignal reply:
5265636569766564207265706c792061667465722061204c6f67346a207061796c6f61642066726f6d207468697320686f73740a4f7269676e616c20726571756573742077617320746f203139352e3133302e3231372e3138340a
Found by Log4JOpportunistic 2021-12-10
Report created by
BloodyShell
2021-12-11
BloodyShell
2021-12-11
Report approved by
BloodyShell
2021-12-11
BloodyShell
2021-12-11
New PDF report generated by system 2021-12-11
Report dispatched to ...@... by system 2021-12-11
Report comment dispatched to BloodyShell by system 2021-12-15
Report comment dispatched to iampritam by system 2021-12-15
Report comment dispatched to zythop by system 2021-12-15
Report comment dispatched to fokoil by system 2021-12-15
Report comment dispatched to thLambda by system 2021-12-15
Report marked as fixed by
BloodyShell
2022-01-06
BloodyShell
2022-01-06
Report closed by
BloodyShell
2022-01-06
BloodyShell
2022-01-06
New PDF report generated by system 2022-01-06
Information
Owner
Mimecast
Created
2021-12-11 01:08
Updated
2022-01-13 13:19
Fixed
true
Contacts
d...@mimecast.com
Status
Status
closed
Hosting contacted
false
CERT contacted
false
Download report