Help
RSS
API
Feed
Maltego
Contact
Domain > reload4j.qos.ch
×
Welcome!
Right click nodes and scroll the mouse to navigate the graph.
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2025-01-27
195.15.222.169
(
ClassC
)
Port 80
HTTP/1.1 301 Moved PermanentlyDate: Mon, 02 Sep 2024 02:14:44 GMTServer: Apache/2.4.62 (Debian)Location: https://reload4j.qos.ch/Content-Length: 313Content-Type: text/html; charsetiso-8859-1 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN>html>head>title>301 Moved Permanently/title>/head>body>h1>Moved Permanently/h1>p>The document has moved a hrefhttps://reload4j.qos.ch/>here/a>./p>hr>address>Apache/2.4.62 (Debian) Server at reload4j.qos.ch Port 80/address>/body>/html>
Port 443
HTTP/1.1 200 OKDate: Mon, 02 Sep 2024 02:14:45 GMTServer: Apache/2.4.62 (Debian)Last-Modified: Thu, 11 Apr 2024 13:54:09 GMTETag: 43b6-615d27d44a262Accept-Ranges: bytesContent-Length: 17334Vary: Accep !DOCTYPE html>html langen>head> meta charsetUTF-8> meta nameviewport contentwidthdevice-width, initial-scale1> title>reload4j/title> script typetext/javascript>prefix;/script>/head>body onLoadenableMenuEventListeners(); hljs.highlightAll(); decorate();>script srctemplates/header3.js typetext/javascript>/script> div idcontent> script typetext/javascript srctemplates/sponsoredBy.js >/script> h2>reload4j project/h2> p>Initiated by Ceki Gülcü, the original author of Apache log4j 1.x, the reload4j project is a fork of Apache log4j version 1.2.17 with the goal of fixing pressing security issues. Reload4j is a span classgreen big>binary compatible/span>, drop-in replacement for log4j version 1.2.17. By drop-in, we mean that you can replace em>log4j.jar/em> with em>reload4j.jar/em> in your build with no source code changes, no recompilation, nor rebuild being necessary. /p> p>The reload4j project offers a clear and easy migration path for the thousands of users who have an urgent need to fix vulnerabilities in log4j 1.2.17. /p> p classbig>Please note that neither log4j 1.x nor reload4j offer a message lookup mechanism. It follows that they do span classbig green>not/span> and did span classbig green>not/span> suffer from the infamous a hrefhttps://www.slf4j.org/log4shell.html>log4shell/a> vulnerability./p> h3>Goals/h3> p>As mentioned above, the reload4j project aims to fix the most urgent issues in log4j 1.2.17. This is accomplished by the following steps:/p> ul> li>Standardize and a hrefhttps://github.com/qos-ch/reload4j/issues/1>sanitize/a> the build - fixed in 1.2.18.0/li> li>a hrefhttps://cve.report/CVE-2021-4104>CVE-2021-4104 (JMSAppender)/a> - fixed in 1.2.18.0 by hardening/li> li>a hrefhttps://cve.report/CVE-2022-23302>CVE-2022-23302 (JMSSink)/a> - fixed in 1.2.18.1 by hardening/li> li>a hrefhttps://cve.report/CVE-2019-17571>CVE-2019-17571 (SocketServer)/a> - fixed in 1.2.18.0 by hardening/li> li>a hrefhttps://cve.report/CVE-2020-9493>CVE-2020
View on OTX
|
View on ThreatMiner
Please enable JavaScript to view the
comments powered by Disqus.
Data with thanks to
AlienVault OTX
,
VirusTotal
,
Malwr
and
others
. [
Sitemap
]