<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/" >

<channel>
	<title>apache &#8211; AnonyViet</title>
	<atom:link href="https://anonyviet.com/tag/apache/feed/" rel="self" type="application/rss+xml" />
	<link>https://anonyviet.com</link>
	<description>Webiste chia sẻ kiến thức công nghệ thông tin, mạng máy tính, bảo mật phổ biến nhất Việt Nam. Luôn cập nhật tin tức, thủ thuật nóng hổi nhất</description>
	<lastBuildDate>Thu, 24 Jul 2025 11:46:25 +0000</lastBuildDate>
	<language>vi</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://anonyviet.com/wp-content/uploads/2018/10/cropped-ico-logo-75x75.png</url>
	<title>apache &#8211; AnonyViet</title>
	<link>https://anonyviet.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Cách sửa lỗi bảo mật Log4j nếu bạn không thể Update lên 2.15.0</title>
		<link>https://anonyviet.com/cach-sua-loi-bao-mat-log4j-neu-ban-khong-the-update-len-ban-moi-nhat/</link>
					<comments>https://anonyviet.com/cach-sua-loi-bao-mat-log4j-neu-ban-khong-the-update-len-ban-moi-nhat/#respond</comments>
		
		<dc:creator><![CDATA[Ellyx13]]></dc:creator>
		<pubDate>Mon, 13 Dec 2021 23:59:09 +0000</pubDate>
				<category><![CDATA[Tin tức]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[CVE-2021-44228]]></category>
		<category><![CDATA[lỗ hổng bảo mật]]></category>
		<category><![CDATA[Log4j]]></category>
		<guid isPermaLink="false">https://anonyviet.com/?p=37982</guid>

					<description><![CDATA[Các nhà nghiên cứu đã phát hiện ra một lỗ hổng nghiêm trọng trong thư viện Apache Log4j, có điểm 10/10 trong CVSS. Dưới đây là bài phân tích và hướng dẫn bạn bảo vệ máy chủ. Nhiều hãng tin tức bảo mật đã đưa tin về việc phát hiện ra lỗ hổng nghiêm trọng [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Các nhà nghiên cứu đã phát hiện ra một lỗ hổng nghiêm trọng trong thư viện Apache Log4j, có điểm 10/10 trong CVSS. Dưới đây là bài phân tích và hướng dẫn bạn bảo vệ máy chủ.</p>
<p><img fetchpriority="high" decoding="async" class="aligncenter  size-full" src="https://anonyviet.com/wp-content/uploads/2021/12/Log4j-blog-post.jpg" alt="Lỗ hổng nghiêm trọng trong thư viện Apache Log4j" width="1000" height="650" title="Cách sửa lỗi bảo mật Log4j nếu bạn không thể Update lên 2.15.0 2"></p>
<p>Nhiều hãng tin tức bảo mật đã đưa tin về việc phát hiện ra lỗ hổng nghiêm trọng CVE-2021-44228 trong thư viện Apache Log4j (mức độ nghiêm trọng CVSS 10/10). Hàng triệu ứng dụng Java sử dụng thư viện này để ghi lại các thông báo lỗi. Để làm cho vấn đề tồi tệ hơn, những kẻ tấn công đã tích cực khai thác lỗ hổng này. Vì lý do này, Apache Foundation khuyến nghị tất cả các nhà phát triển cập nhật thư viện lên phiên bản 2.15.0 và nếu không được, hãy sử dụng một trong các phương pháp <a href="https://logging.apache.org/log4j/2.x/security.html" rel="noopener">tại đây</a>.</p>
<h2>Tại sao CVE-2021-44228 lại nguy hiểm đến vậy</h2>
<p>CVE-2021-44228, còn được đặt tên là Log4Shell hoặc LogJam, là một lỗ hổng trong lớp Remote Code Execution (RCE). Nếu những kẻ tấn công khai thác nó trên các máy chủ, chúng sẽ có thể thực thi code tùy ý và có khả năng kiểm soát toàn bộ hệ thống.</p>
<p>Điều khiến CVE-2021-44228 trở nên đặc biệt nguy hiểm là tính dễ bị khai thác: ngay cả một hacker thiếu kinh nghiệm cũng có thể thực hiện thành công một cuộc tấn công bằng cách sử dụng lỗ hổng này. Theo các nhà nghiên cứu, những kẻ tấn công chỉ cần buộc ứng dụng chỉ ghi một chuỗi vào nhật ký và sau đó chúng có thể tải code của chính mình lên ứng dụng nhờ chức năng thay thế tra cứu tin nhắn.</p>
<p>Cách bài viết hướng dẫn tấn công <a href="https://tophuongloan.com/poc-la-gi/" rel="noopener">Proofs of Concept (PoC)</a> thông qua CVE-2021-44228 đều đã có sẵn trên Internet. Do đó, không có gì ngạc nhiên khi các công ty an ninh mạng đã thực hiện các đợt quét mạng khổng lồ để tìm các ứng dụng dễ bị tấn công cũng như các cuộc tấn công vào honeypots.</p>
<p>Lỗ hổng này được phát hiện bởi Chen Zhaojun thuộc Đội bảo mật đám mây của Alibaba.</p>
<h2>Apache Log4J là gì và tại sao thư viện này lại phổ biến như vậy?</h2>
<p>Apache Log4j là một phần của Dự án Apache Logging. Nhìn chung, việc sử dụng thư viện này là một trong những cách dễ nhất để ghi lại lỗi và đó là lý do tại sao hầu hết các nhà phát triển Java sử dụng nó.</p>
<p>Nhiều công ty phần mềm lớn và dịch vụ trực tuyến sử dụng thư viện Log4j, bao gồm Amazon, Apple iCloud, Cisco, Cloudflare, ElasticSearch, Red Hat, Steam, Tesla, Twitter,&#8230; Do thư viện này quá phổ biến, nên một số nhà nghiên cứu bảo mật thông tin dự kiến ​​sẽ các cuộc tấn công vào các máy chủ dễ bị tấn công sẽ gia tăng đáng kể  trong những ngày tới.</p>
<blockquote class="twitter-tweet" data-width="500" data-dnt="true">
<p lang="qme" dir="ltr"><a href="https://twitter.com/hashtag/Log4Shell?src=hash&amp;ref_src=twsrc%5Etfw" rel="noopener">#Log4Shell</a> <a href="https://t.co/1bKDwRQBqt">pic.twitter.com/1bKDwRQBqt</a></p>
<p>&mdash; Florian Roth (@cyb3rops) <a href="https://twitter.com/cyb3rops/status/1469326219174891520?ref_src=twsrc%5Etfw" rel="noopener">December 10, 2021</a></p></blockquote>
<p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></p>
<h2>Phiên bản nào của thư viện Log4j dễ bị tấn công và cách để bạn bảo vệ Server?</h2>
<p>Hầu như tất cả các phiên bản của Log4j đều dễ bị tấn công, bắt đầu từ 2.0-beta9 đến 2.14.1. Phương pháp bảo vệ đơn giản và hiệu quả nhất là cài đặt phiên bản mới nhất của thư viện, 2.15.0. Bạn có thể tải xuống trên trang<a href="https://logging.apache.org/log4j/2.x/download.html" rel="noopener"> dự án</a>.</p>
<p>Nếu vì lý do nào đó mà việc cập nhật thư viện không thể thực hiện được, Apache Foundation khuyên bạn nên sử dụng một trong các phương pháp giảm thiểu sau. Trong trường hợp các phiên bản Log4J từ 2.10 đến 2.14.1, họ khuyên bạn nên đặt thuộc tính hệ thống <strong>log4j2.formatMsgNoLookups</strong> hoặc đặt biến môi trường <strong>LOG4J_FORMAT_MSG_NO_LOOKUPS</strong> thành <strong>true</strong>.</p>
<p>Để bảo vệ các bản phát hành trước đó của Log4j (từ 2.0-beta9 đến 2.10.0), các nhà phát triển thư viện khuyên bạn nên xóa class JndiLookup khỏi classpath: <strong>zip -q -d log4j-core – *. Jar org / apache / logging / log4j / core / lookup / JndiLookup .class</strong>.</p>
<p>Ngoài ra, bạn cũng nên xem <a href="https://anonyviet.com/phuong-phap-bao-mat-giup-an-toan-tren-internet/">những phương pháp bảo mật này để bảo vệ bản thân tốt hơn</a>.</p>
<h2>Danh sách các hãng bị ảnh hưởng bởi lỗ hổng Log4j</h2>
<h3><strong>A</strong></h3>
<p><strong>Akamai : <a href="https://www.akamai.com/blog/news/CVE-2021-44228-Zero-Day-Vulnerability" rel="noopener">https://www.akamai.com/blog/news/CVE-2021-44228-Zero-Day-Vulnerability</a></strong></p>
<p><strong>Apache Druid : <a href="https://github.com/apache/druid/pull/12051" rel="noopener">https://github.com/apache/druid/pull/12051</a></strong></p>
<p><strong>Apache Flink : <a href="https://flink.apache.org/2021/12/10/log4j-cve.html" rel="noopener">https://flink.apache.org/2021/12/10/log4j-cve.html</a></strong></p>
<p><strong>Apache Guacamole <a href="https://issues.apache.org/jira/projects/GUACAMOLE/issues/GUACAMOLE-1474?filter=allissues" rel="noopener">https://issues.apache.org/jira/projects/GUACAMOLE/issues/GUACAMOLE-1474?filter=allissues</a></strong></p>
<p><strong>Apache LOG4J : <a href="https://logging.apache.org/log4j/2.x/security.html" rel="noopener">https://logging.apache.org/log4j/2.x/security.html</a></strong></p>
<p><strong>Apache Kafka : <a href="https://lists.apache.org/thread/lgbtvvmy68p0059yoyn9qxzosdmx4jdv" rel="noopener">https://lists.apache.org/thread/lgbtvvmy68p0059yoyn9qxzosdmx4jdv</a></strong></p>
<p><strong>Apache Solr : <a href="https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-cve-2021-44228" rel="noopener">https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-cve-2021-44228</a></strong></p>
<p><strong>Apache Struts : <a href="https://struts.apache.org/announce-2021#a20211212-2" rel="noopener">https://struts.apache.org/announce-2021#a20211212-2</a></strong></p>
<p><strong>Apero CAS : <a href="https://apereo.github.io/2021/12/11/log4j-vuln/" rel="noopener">https://apereo.github.io/2021/12/11/log4j-vuln/</a></strong></p>
<p><strong>Apigee : <a href="https://status.apigee.com/incidents/3cgzb0q2r10p" rel="noopener">https://status.apigee.com/incidents/3cgzb0q2r10p</a></strong></p>
<p><strong>Appdynamics : <a href="https://docs.appdynamics.com/display/PAA/Security+Advisory%3A+Apache+Log4j+Vulnerability" rel="noopener">https://docs.appdynamics.com/display/PAA/Security+Advisory%3A+Apache+Log4j+Vulnerability</a></strong></p>
<p><strong>APPSHEET : <a href="https://community.appsheet.com/t/appsheet-statement-on-log4j-vulnerability-cve-2021-44228/59976" rel="noopener">https://community.appsheet.com/t/appsheet-statement-on-log4j-vulnerability-cve-2021-44228/59976</a></strong></p>
<p><strong>Aptible : <a href="https://status.aptible.com/incidents/gk1rh440h36s?u=zfbcrbt2lkv4" rel="noopener">https://status.aptible.com/incidents/gk1rh440h36s?u=zfbcrbt2lkv4</a></strong></p>
<p><strong>Ariba : <a href="https://connectsupport.ariba.com/sites#announcements-display&amp;/Event/908469" rel="noopener">https://connectsupport.ariba.com/sites#announcements-display&amp;/Event/908469</a></strong></p>
<p><strong>Arista : <a href="https://www.arista.com/en/support/advisories-notices/security-advisories/13425-security-advisory-0070" rel="noopener">https://www.arista.com/en/support/advisories-notices/security-advisories/13425-security-advisory-0070</a></strong></p>
<p><strong>ArrayNetworks : <a href="https://twitter.com/ArraySupport/status/1470141638571745282" rel="noopener">https://twitter.com/ArraySupport/status/1470141638571745282</a></strong></p>
<p><strong>Atlassian : <a href="https://confluence.atlassian.com/kb/faq-for-cve-2021-44228-1103069406.html" rel="noopener">https://confluence.atlassian.com/kb/faq-for-cve-2021-44228-1103069406.html</a></strong></p>
<p><strong>Automox : <a href="https://blog.automox.com/log4j-critical-vulnerability-scores-a-10" rel="noopener">https://blog.automox.com/log4j-critical-vulnerability-scores-a-10</a></strong></p>
<p><strong>Avantra SYSLINK : <a href="https://support.avantra.com/support/solutions/articles/44002291388-cve-2021-44228-log4j-2-vulnerability" rel="noopener">https://support.avantra.com/support/solutions/articles/44002291388-cve-2021-44228-log4j-2-vulnerability</a></strong></p>
<p><strong>Avaya : <a href="https://support.avaya.com/helpcenter/getGenericDetails?detailId=1399839287609" rel="noopener">https://support.avaya.com/helpcenter/getGenericDetails?detailId=1399839287609</a></strong></p>
<p><strong>AVM UNOFICIAl : <a href="https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592#gistcomment-3993316" rel="noopener">https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592#gistcomment-3993316</a></strong></p>
<p><strong>AWS New : <a href="https://aws.amazon.com/security/security-bulletins/AWS-2021-006/" rel="noopener">https://aws.amazon.com/security/security-bulletins/AWS-2021-006/</a></strong></p>
<p><strong>AWS OLD: <a href="https://aws.amazon.com/security/security-bulletins/AWS-2021-005/" rel="noopener">https://aws.amazon.com/security/security-bulletins/AWS-2021-005/</a></strong></p>
<p><strong>AZURE Datalake store java : <a href="https://github.com/Azure/azure-data-lake-store-java/blob/ed5d6304783286c3cfff0a1dee457a922e23ad48/CHANGES.md#version-2310" rel="noopener">https://github.com/Azure/azure-data-lake-store-java/blob/ed5d6304783286c3cfff0a1dee457a922e23ad48/CHANGES.md#version-2310</a></strong></p>
<h3><strong>B</strong></h3>
<p><strong>BACKBLAZE : <a href="https://twitter.com/backblaze/status/1469477224277368838" rel="noopener">https://twitter.com/backblaze/status/1469477224277368838</a></strong></p>
<p><strong>BeyondTrust Bomgar : <a href="https://beyondtrustcorp.service-now.com/kb_view.do?sysparm_article=KB0016542" rel="noopener">https://beyondtrustcorp.service-now.com/kb_view.do?sysparm_article=KB0016542</a></strong></p>
<p><strong>BigBlueButton : <a href="https://github.com/bigbluebutton/bigbluebutton/issues/13897#issuecomment-991652632" rel="noopener">https://github.com/bigbluebutton/bigbluebutton/issues/13897#issuecomment-991652632</a></strong></p>
<p><strong>BitDefender : <a href="https://businessinsights.bitdefender.com/security-advisory-bitdefender-response-to-critical-0-day-apache-log4j2-vulnerability" rel="noopener">https://businessinsights.bitdefender.com/security-advisory-bitdefender-response-to-critical-0-day-apache-log4j2-vulnerability</a></strong></p>
<p><strong>BitNami By VMware : <a href="https://docs.bitnami.com/general/security/security-2021-12-10/" rel="noopener">https://docs.bitnami.com/general/security/security-2021-12-10/</a></strong></p>
<p><strong>BMC Software : <a href="https://community.bmc.com/s/news/aA33n000000TSUdCAO/bmc-security-advisory-for-cve202144228-log4shell-vulnerability" rel="noopener">https://community.bmc.com/s/news/aA33n000000TSUdCAO/bmc-security-advisory-for-cve202144228-log4shell-vulnerability</a></strong></p>
<p><strong>Boomi DELL : <a href="https://community.boomi.com/s/question/0D56S00009UQkx4SAD/is-boomi-installation-moleculegateway-protected-from-cve202144228-log4j" rel="noopener">https://community.boomi.com/s/question/0D56S00009UQkx4SAD/is-boomi-installation-moleculegateway-protected-from-cve202144228-log4j</a></strong></p>
<p><strong>Broadcom : <a href="https://support.broadcom.com/security-advisory/content/security-advisories/Symantec-Security-Advisory-for-Log4j-2-CVE-2021-44228-Vulnerability/SYMSA19793" rel="noopener">https://support.broadcom.com/security-advisory/content/security-advisories/Symantec-Security-Advisory-for-Log4j-2-CVE-2021-44228-Vulnerability/SYMSA19793</a></strong></p>
<p><strong>Broadcom Automic Automation : <a href="https://knowledge.broadcom.com/external/article?articleId=230308" rel="noopener">https://knowledge.broadcom.com/external/article?articleId=230308</a></strong></p>
<h3><strong>C</strong></h3>
<p><strong>Camunda : <a href="https://forum.camunda.org/t/cve-2021-44228-log4j-2-exploit/31871/4" rel="noopener">https://forum.camunda.org/t/cve-2021-44228-log4j-2-exploit/31871/4</a></strong></p>
<p><strong>CarbonBlack : <a href="https://community.carbonblack.com/t5/Threat-Research-Docs/Log4Shell-Log4j-Remote-Code-Execution-CVE-2021-44228/ta-p/109134" rel="noopener">https://community.carbonblack.com/t5/Threat-Research-Docs/Log4Shell-Log4j-Remote-Code-Execution-CVE-2021-44228/ta-p/109134</a></strong></p>
<p><strong>Cerberus FTP : <a href="https://support.cerberusftp.com/hc/en-us/articles/4412448183571-Cerberus-is-not-affected-by-CVE-2021-44228-log4j-0-day-vulnerability" rel="noopener">https://support.cerberusftp.com/hc/en-us/articles/4412448183571-Cerberus-is-not-affected-by-CVE-2021-44228-log4j-0-day-vulnerability</a></strong></p>
<p><strong>ChaserSystems : <a href="https://chasersystems.com/discrimiNAT/blog/log4shell-and-its-traces-in-a-network-egress-filter/#are-chasers-products-affected" rel="noopener">https://chasersystems.com/discrimiNAT/blog/log4shell-and-its-traces-in-a-network-egress-filter/#are-chasers-products-affected</a></strong></p>
<p><strong>CheckPoint : <a href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;solutionid=sk176865&amp;partition=General&amp;product=IPS" rel="noopener">https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;solutionid=sk176865&amp;partition=General&amp;product=IPS</a></strong></p>
<p><strong>Cisco: <a href="https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd" rel="noopener">https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd</a></strong></p>
<p><strong>Citrix : <a href="https://support.citrix.com/article/CTX335705" rel="noopener">https://support.citrix.com/article/CTX335705</a></strong></p>
<p><strong>CloudFlare : <a href="https://blog.cloudflare.com/cve-2021-44228-log4j-rce-0-day-mitigation/" rel="noopener">https://blog.cloudflare.com/cve-2021-44228-log4j-rce-0-day-mitigation/</a></strong></p>
<p><strong>Cloudian HyperStore : <a href="https://cloudian-support.force.com/s/article/SECURITY-Cloudian-HyperStore-Log4j-vulnerability-CVE-2021-44228" rel="noopener">https://cloudian-support.force.com/s/article/SECURITY-Cloudian-HyperStore-Log4j-vulnerability-CVE-2021-44228</a></strong></p>
<p><strong>CPanel : <a href="https://forums.cpanel.net/threads/log4j-cve-2021-44228-does-it-affect-cpanel.696249/" rel="noopener">https://forums.cpanel.net/threads/log4j-cve-2021-44228-does-it-affect-cpanel.696249/</a></strong></p>
<p><strong>Code42 : <a href="https://support.code42.com/Terms_and_conditions/Code42_customer_support_resources/Code42_response_to_industry_security_incidents" rel="noopener">https://support.code42.com/Terms_and_conditions/Code42_customer_support_resources/Code42_response_to_industry_security_incidents</a></strong></p>
<p><strong>CommVault <a href="https://community.commvault.com/technical-q-a-2/log4j-been-used-in-commvault-1985?postid=11745#post11745" rel="noopener">https://community.commvault.com/technical-q-a-2/log4j-been-used-in-commvault-1985?postid=11745#post11745</a></strong></p>
<p><strong>ConcreteCMS.com : <a href="https://www.concretecms.com/about/blog/security/concrete-log4j-zero-day-exploit" rel="noopener">https://www.concretecms.com/about/blog/security/concrete-log4j-zero-day-exploit</a></strong></p>
<p><strong>Connect2id : <a href="https://connect2id.com/blog/connect2id-server-12-5-1" rel="noopener">https://connect2id.com/blog/connect2id-server-12-5-1</a></strong></p>
<p><strong>ConnectWise : <a href="https://www.connectwise.com/company/trust/advisories" rel="noopener">https://www.connectwise.com/company/trust/advisories</a></strong></p>
<p><strong>ContrastSecurity : <a href="https://support.contrastsecurity.com/hc/en-us/articles/4412612486548" rel="noopener">https://support.contrastsecurity.com/hc/en-us/articles/4412612486548</a></strong></p>
<p><strong>ControlUp : <a href="https://status.controlup.com/incidents/qqyvh7b1dz8k" rel="noopener">https://status.controlup.com/incidents/qqyvh7b1dz8k</a></strong></p>
<p><strong>Coralogix : <a href="https://twitter.com/Coralogix/status/1469713430659559425" rel="noopener">https://twitter.com/Coralogix/status/1469713430659559425</a></strong></p>
<p><strong>CouchBase : <a href="https://forums.couchbase.com/t/ann-elasticsearch-connector-4-3-3-4-2-13-fixes-log4j-vulnerability/32402" rel="noopener">https://forums.couchbase.com/t/ann-elasticsearch-connector-4-3-3-4-2-13-fixes-log4j-vulnerability/32402</a></strong></p>
<p><strong>CryptShare : <a href="https://www.cryptshare.com/en/support/cryptshare-support/#c67572" rel="noopener">https://www.cryptshare.com/en/support/cryptshare-support/#c67572</a></strong></p>
<p><strong>CyberArk : <a href="https://cyberark-customers.force.com/s/article/Critical-Vulnerability-CVE-2021-44228" rel="noopener">https://cyberark-customers.force.com/s/article/Critical-Vulnerability-CVE-2021-44228</a></strong></p>
<p><strong>Cybereason : <a href="https://www.cybereason.com/blog/cybereason-solutions-are-not-impacted-by-apache-log4j-vulnerability-cve-2021-44228" rel="noopener">https://www.cybereason.com/blog/cybereason-solutions-are-not-impacted-by-apache-log4j-vulnerability-cve-2021-44228</a></strong></p>
<h3><strong>D</strong></h3>
<p><strong>Dataminer : <a href="https://community.dataminer.services/responding-to-log4shell-vulnerability/" rel="noopener">https://community.dataminer.services/responding-to-log4shell-vulnerability/</a></strong></p>
<p><strong>Datto : <a href="https://www.datto.com/blog/dattos-response-to-log4shell" rel="noopener">https://www.datto.com/blog/dattos-response-to-log4shell</a></strong></p>
<p><strong>Debian : <a href="https://security-tracker.debian.org/tracker/CVE-2021-44228" rel="noopener">https://security-tracker.debian.org/tracker/CVE-2021-44228</a></strong></p>
<p><strong>Dell : <a href="https://www.dell.com/support/kbdoc/fr-fr/000194372/dsn-2021-007-dell-response-to-apache-log4j-remote-code-execution-vulnerability" rel="noopener">https://www.dell.com/support/kbdoc/fr-fr/000194372/dsn-2021-007-dell-response-to-apache-log4j-remote-code-execution-vulnerability</a></strong></p>
<p><strong>DELL : <a href="https://www.dell.com/support/kbdoc/en-uk/000194416/additional-information-for-apache-log4j-remote-code-execution-vulnerability-cve-2021-44228" rel="noopener">https://www.dell.com/support/kbdoc/en-uk/000194416/additional-information-for-apache-log4j-remote-code-execution-vulnerability-cve-2021-44228</a></strong></p>
<p><strong>Docker : <a href="https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/" rel="noopener">https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/</a></strong></p>
<p><strong>Docusign : <a href="https://www.docusign.com/trust/alerts/alert-docusign-statement-on-the-log4j2-vulnerability" rel="noopener">https://www.docusign.com/trust/alerts/alert-docusign-statement-on-the-log4j2-vulnerability</a></strong></p>
<p><strong>dCache.org : <a href="https://www.dcache.org/post/log4j-vulnerability/" rel="noopener">https://www.dcache.org/post/log4j-vulnerability/</a></strong></p>
<p><strong>DCM4CHE.org : <a href="https://github.com/dcm4che/dcm4che/issues/1050" rel="noopener">https://github.com/dcm4che/dcm4che/issues/1050</a></strong></p>
<p><strong>DRAW.IO : <a href="https://twitter.com/drawio/status/1470061320066277382" rel="noopener">https://twitter.com/drawio/status/1470061320066277382</a></strong></p>
<p><strong>DropWizard : <a href="https://twitter.com/dropwizardio/status/1469285337524580359" rel="noopener">https://twitter.com/dropwizardio/status/1469285337524580359</a></strong></p>
<p><strong>DynaTrace : <a href="https://community.dynatrace.com/t5/Dynatrace-Open-Q-A/Impact-of-log4j-zero-day-vulnerability/m-p/177259/highlight/true#M19282" rel="noopener">https://community.dynatrace.com/t5/Dynatrace-Open-Q-A/Impact-of-log4j-zero-day-vulnerability/m-p/177259/highlight/true#M19282</a></strong></p>
<h3><strong>E</strong></h3>
<p><strong>Eclipse Foundation : <a href="https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592#gistcomment-3992521" rel="noopener">https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592#gistcomment-3992521</a></strong></p>
<p><strong>EHRBase : <a href="https://github.com/ehrbase/ehrbase/issues/700" rel="noopener">https://github.com/ehrbase/ehrbase/issues/700</a></strong></p>
<p><strong>Elastic : <a href="https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476" rel="noopener">https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476</a></strong></p>
<p><strong>ESET : <a href="https://forum.eset.com/topic/30691-log4j-vulnerability/?do=findComment&amp;comment=143745" rel="noopener">https://forum.eset.com/topic/30691-log4j-vulnerability/?do=findComment&amp;comment=143745</a></strong></p>
<p><strong>ESRI : <a href="https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/arcgis-software-and-cve-2021-44228-aka-log4shell-aka-logjam/" rel="noopener">https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/arcgis-software-and-cve-2021-44228-aka-log4shell-aka-logjam/</a></strong></p>
<p><strong>EVLLABS JGAAP : <a href="https://github.com/evllabs/JGAAP/releases/tag/v8.0.2" rel="noopener">https://github.com/evllabs/JGAAP/releases/tag/v8.0.2</a></strong></p>
<p><strong>Extreme Networks : <a href="https://extremeportal.force.com/ExtrArticleDetail?an=000100806" rel="noopener">https://extremeportal.force.com/ExtrArticleDetail?an=000100806</a></strong></p>
<p><strong>F</strong></p>
<p><strong>F5 Networks : <a href="https://support.f5.com/csp/article/K19026212" rel="noopener">https://support.f5.com/csp/article/K19026212</a></strong></p>
<p><strong>F-Secure <a href="https://status.f-secure.com/incidents/sk8vmr0h34pd" rel="noopener">https://status.f-secure.com/incidents/sk8vmr0h34pd</a></strong></p>
<p><strong>Fastly : <a href="https://www.fastly.com/blog/digging-deeper-into-log4shell-0day-rce-exploit-found-in-log4j" rel="noopener">https://www.fastly.com/blog/digging-deeper-into-log4shell-0day-rce-exploit-found-in-log4j</a></strong></p>
<p><strong>ForcePoint : <a href="https://support.forcepoint.com/s/article/CVE-2021-44228-Java-log4j-vulnerability-mitigation-with-Forcepoint-Security-Manager" rel="noopener">https://support.forcepoint.com/s/article/CVE-2021-44228-Java-log4j-vulnerability-mitigation-with-Forcepoint-Security-Manager</a></strong></p>
<p><strong>Forescout : <a href="https://forescout.force.com/support/s/article/Important-security-information-related-to-Apache-Log4j-utility-CVE-2021-44228" rel="noopener">https://forescout.force.com/support/s/article/Important-security-information-related-to-Apache-Log4j-utility-CVE-2021-44228</a></strong></p>
<p><strong>ForgeRock : <a href="https://backstage.forgerock.com/knowledge/kb/book/b21824339" rel="noopener">https://backstage.forgerock.com/knowledge/kb/book/b21824339</a></strong></p>
<p><strong>Fortinet : <a href="https://www.fortiguard.com/psirt/FG-IR-21-245" rel="noopener">https://www.fortiguard.com/psirt/FG-IR-21-245</a></strong></p>
<p><strong>FTAPI : <a href="https://docs.ftapi.com/display/RN/4.12.2" rel="noopener">https://docs.ftapi.com/display/RN/4.12.2</a></strong></p>
<p><strong>FusionAuth : <a href="https://fusionauth.io/blog/2021/12/10/log4j-fusionauth/" rel="noopener">https://fusionauth.io/blog/2021/12/10/log4j-fusionauth/</a></strong></p>
<h3><strong>G</strong></h3>
<p><strong>Gearset : <a href="https://docs.gearset.com/en/articles/5806813-gearset-log4j-statement-dec-2021" rel="noopener">https://docs.gearset.com/en/articles/5806813-gearset-log4j-statement-dec-2021</a></strong></p>
<p><strong>Genesys : <a href="https://www.genesys.com/blog/post/genesys-update-on-the-apache-log4j-vulnerability" rel="noopener">https://www.genesys.com/blog/post/genesys-update-on-the-apache-log4j-vulnerability</a></strong></p>
<p><strong>Ghidra : <a href="https://github.com/NationalSecurityAgency/ghidra/blob/2c73c72f0ba2720c6627be4005a721a5ebd64b46/README.md#warning" rel="noopener">https://github.com/NationalSecurityAgency/ghidra/blob/2c73c72f0ba2720c6627be4005a721a5ebd64b46/README.md#warning</a></strong></p>
<p><strong>GitHub : <a href="https://github.com/advisories/GHSA-jfh8-c2jp-5v3q" rel="noopener">https://github.com/advisories/GHSA-jfh8-c2jp-5v3q</a></strong></p>
<p><strong>GoAnywhere : <a href="https://www.goanywhere.com/cve-2021-44228-goanywhere-mitigation-steps" rel="noopener">https://www.goanywhere.com/cve-2021-44228-goanywhere-mitigation-steps</a></strong></p>
<p><strong>Google Cloud Global Products coverage : <a href="https://cloud.google.com/log4j2-security-advisory" rel="noopener">https://cloud.google.com/log4j2-security-advisory</a></strong></p>
<p><strong>Google Cloud Armor WAF : <a href="https://cloud.google.com/blog/products/identity-security/cloud-armor-waf-rule-to-help-address-apache-log4j-vulnerability" rel="noopener">https://cloud.google.com/blog/products/identity-security/cloud-armor-waf-rule-to-help-address-apache-log4j-vulnerability</a></strong></p>
<p><strong>GrayLog : <a href="https://www.graylog.org/post/graylog-update-for-log4j" rel="noopener">https://www.graylog.org/post/graylog-update-for-log4j</a></strong></p>
<p><strong>GratWiFi WARNING I can&#8217;t confirm it: <a href="https://www.facebook.com/GratWiFi/posts/396447615600785" rel="noopener">https://www.facebook.com/GratWiFi/posts/396447615600785</a></strong></p>
<p><strong>GuardedBox : <a href="https://twitter.com/GuardedBox/status/1469739834117799939" rel="noopener">https://twitter.com/GuardedBox/status/1469739834117799939</a></strong></p>
<p><strong>Guidewire : <a href="https://community.guidewire.com/s/article/Update-to-customers-who-have-questions-about-the-use-of-log4j-in-Guidewire-products" rel="noopener">https://community.guidewire.com/s/article/Update-to-customers-who-have-questions-about-the-use-of-log4j-in-Guidewire-products</a></strong></p>
<h3><strong>H</strong></h3>
<p><strong>HackerOne : <a href="https://twitter.com/jobertabma/status/1469490881854013444" rel="noopener">https://twitter.com/jobertabma/status/1469490881854013444</a></strong></p>
<p><strong>HCL Software : <a href="https://support.hcltechsw.com/csm?id=kb_article&amp;sysparm_article=KB0095486" rel="noopener">https://support.hcltechsw.com/csm?id=kb_article&amp;sysparm_article=KB0095486</a></strong></p>
<p><strong>Hewlett Packard Enterprise HPE : <a href="https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;docId=a00120086en_us" rel="noopener">https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;docId=a00120086en_us</a></strong></p>
<p><strong>Hitachi Vantara : <a href="https://knowledge.hitachivantara.com/Support_Information/Hitachi_Vantara_Security_Advisories/CVE-2021-44228_-_Apache_Log4j2" rel="noopener">https://knowledge.hitachivantara.com/Support_Information/Hitachi_Vantara_Security_Advisories/CVE-2021-44228_-_Apache_Log4j2</a></strong></p>
<p><strong>HostiFi : <a href="https://twitter.com/hostifi_net/status/1469511114824339464" rel="noopener">https://twitter.com/hostifi_net/status/1469511114824339464</a></strong></p>
<p><strong>Huawei : <a href="https://www.huawei.com/en/psirt/security-notices/huawei-sn-20211210-01-log4j2-en" rel="noopener">https://www.huawei.com/en/psirt/security-notices/huawei-sn-20211210-01-log4j2-en</a></strong></p>
<p><strong>I</strong></p>
<p><strong>I2P : <a href="https://geti2p.net/en/blog/post/2021/12/11/i2p-unaffected-cve-2021-44228" rel="noopener">https://geti2p.net/en/blog/post/2021/12/11/i2p-unaffected-cve-2021-44228</a></strong></p>
<p><strong>IBM : <a href="https://www.ibm.com/support/pages/node/6525548" rel="noopener">https://www.ibm.com/support/pages/node/6525548</a></strong></p>
<p><strong>Ignite Realtime : <a href="https://discourse.igniterealtime.org/t/openfire-4-6-5-released/91108" rel="noopener">https://discourse.igniterealtime.org/t/openfire-4-6-5-released/91108</a></strong></p>
<p><strong>IManage : <a href="https://help.imanage.com/hc/en-us/articles/4412696236699-ADVISORY-Security-vulnerability-CVE-2021-44228-in-third-party-component-Apache-Log4j2#h_3164fa6c-4717-4aa1-b2dc-d14d4112595e" rel="noopener">https://help.imanage.com/hc/en-us/articles/4412696236699-ADVISORY-Security-vulnerability-CVE-2021-44228-in-third-party-component-Apache-Log4j2#h_3164fa6c-4717-4aa1-b2dc-d14d4112595e</a></strong></p>
<p><strong>Imperva : <a href="https://www.imperva.com/blog/how-were-protecting-customers-staying-ahead-of-cve-2021-44228/" rel="noopener">https://www.imperva.com/blog/how-were-protecting-customers-staying-ahead-of-cve-2021-44228/</a></strong></p>
<p><strong>Inductive Automation : <a href="https://support.inductiveautomation.com/hc/en-us/articles/4416204541709-Regarding-CVE-2021-44228-Log4j-RCE-0-day" rel="noopener">https://support.inductiveautomation.com/hc/en-us/articles/4416204541709-Regarding-CVE-2021-44228-Log4j-RCE-0-day</a></strong></p>
<p><strong>Informatica : <a href="https://network.informatica.com/community/informatica-network/blog/2021/12/10/log4j-vulnerability-update" rel="noopener">https://network.informatica.com/community/informatica-network/blog/2021/12/10/log4j-vulnerability-update</a></strong></p>
<p><strong>Ironnet : <a href="https://www.ironnet.com/blog/ironnet-security-notifications-related-to-log4j-vulnerability" rel="noopener">https://www.ironnet.com/blog/ironnet-security-notifications-related-to-log4j-vulnerability</a></strong></p>
<p><strong>Ivanti : <a href="https://forums.ivanti.com/s/article/CVE-2021-44228-Java-logging-library-log4j-Ivanti-Products-Impact-Mapping?language=en_US" rel="noopener">https://forums.ivanti.com/s/article/CVE-2021-44228-Java-logging-library-log4j-Ivanti-Products-Impact-Mapping?language=en_US</a></strong></p>
<h3><strong>J</strong></h3>
<p><strong>JAMF NATION : <a href="https://community.jamf.com/t5/jamf-pro/third-party-security-issue/td-p/253740" rel="noopener">https://community.jamf.com/t5/jamf-pro/third-party-security-issue/td-p/253740</a></strong></p>
<p><strong>JazzSM DASH IBM : <a href="https://www.ibm.com/support/pages/node/6525552" rel="noopener">https://www.ibm.com/support/pages/node/6525552</a></strong></p>
<p><strong>Jenkins : <a href="https://www.jenkins.io/blog/2021/12/10/log4j2-rce-CVE-2021-44228/" rel="noopener">https://www.jenkins.io/blog/2021/12/10/log4j2-rce-CVE-2021-44228/</a></strong></p>
<p><strong>JetBrains Teamcity : <a href="https://youtrack.jetbrains.com/issue/TW-74298" rel="noopener">https://youtrack.jetbrains.com/issue/TW-74298</a></strong></p>
<p><strong>JFROG : <a href="https://jfrog.com/knowledge-base/general-jfrog-services-are-not-affected-by-vulnerability-cve-2021-44228/" rel="noopener">https://jfrog.com/knowledge-base/general-jfrog-services-are-not-affected-by-vulnerability-cve-2021-44228/</a></strong></p>
<p><strong>Jitsi : <a href="https://github.com/jitsi/security-advisories/blob/4e1ab58585a8a0593efccce77d5d0e22c5338605/advisories/JSA-2021-0004.md" rel="noopener">https://github.com/jitsi/security-advisories/blob/4e1ab58585a8a0593efccce77d5d0e22c5338605/advisories/JSA-2021-0004.md</a></strong></p>
<h3><strong>K</strong></h3>
<p><strong>Kafka Connect CosmosDB : <a href="https://github.com/microsoft/kafka-connect-cosmosdb/blob/0f5d0c9dbf2812400bb480d1ff0672dfa6bb56f0/CHANGELOG.md" rel="noopener">https://github.com/microsoft/kafka-connect-cosmosdb/blob/0f5d0c9dbf2812400bb480d1ff0672dfa6bb56f0/CHANGELOG.md</a></strong></p>
<p><strong>Kaseya : <a href="https://helpdesk.kaseya.com/hc/en-gb/articles/4413449967377-Log4j2-Vulnerability-Assessment" rel="noopener">https://helpdesk.kaseya.com/hc/en-gb/articles/4413449967377-Log4j2-Vulnerability-Assessment</a></strong></p>
<p><strong>Keycloak : <a href="https://github.com/keycloak/keycloak/discussions/9078" rel="noopener">https://github.com/keycloak/keycloak/discussions/9078</a></strong></p>
<p><strong>KEMP : <a href="https://support.kemptechnologies.com/hc/en-us/articles/4416430695437-CVE-2021-44228-Log4j2-Exploit" rel="noopener">https://support.kemptechnologies.com/hc/en-us/articles/4416430695437-CVE-2021-44228-Log4j2-Exploit</a></strong></p>
<p><strong>Komoot Photon : <a href="https://github.com/komoot/photon/issues/620" rel="noopener">https://github.com/komoot/photon/issues/620</a></strong></p>
<h3><strong>L</strong></h3>
<p><strong>Leanix : <a href="https://www.leanix.net/en/blog/log4j-vulnerability-log4shell" rel="noopener">https://www.leanix.net/en/blog/log4j-vulnerability-log4shell</a></strong></p>
<p><strong>LucentSKY : <a href="https://twitter.com/LucentSky/status/1469358706311974914" rel="noopener">https://twitter.com/LucentSky/status/1469358706311974914</a></strong></p>
<p><strong>Lightbend : <a href="https://discuss.lightbend.com/t/regarding-the-log4j2-vulnerability-cve-2021-44228/9275" rel="noopener">https://discuss.lightbend.com/t/regarding-the-log4j2-vulnerability-cve-2021-44228/9275</a></strong></p>
<p><strong>LiquidFiles : <a href="https://mailchi.mp/liquidfiles/liquidfiles-log4j?e=%5BUNIQID%5D" rel="noopener">https://mailchi.mp/liquidfiles/liquidfiles-log4j?e=%5BUNIQID%5D</a></strong></p>
<p><strong>LogRhythm CISO email I can&#8217;t confirmed : <a href="https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592#gistcomment-3992599" rel="noopener">https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592#gistcomment-3992599</a></strong></p>
<h3><strong>M</strong></h3>
<p><strong>Macchina io : <a href="https://twitter.com/macchina_io/status/1469611606569099269" rel="noopener">https://twitter.com/macchina_io/status/1469611606569099269</a></strong></p>
<p><strong>MailCow : <a href="https://github.com/mailcow/mailcow-dockerized/issues/4375" rel="noopener">https://github.com/mailcow/mailcow-dockerized/issues/4375</a></strong></p>
<p><strong>ManageEngine Zoho : <a href="https://pitstop.manageengine.com/portal/en/community/topic/log4j-ad-manager-plus" rel="noopener">https://pitstop.manageengine.com/portal/en/community/topic/log4j-ad-manager-plus</a></strong></p>
<p><strong>ManageEngine Zoho : <a href="https://pitstop.manageengine.com/portal/en/community/topic/log4j-security-issue" rel="noopener">https://pitstop.manageengine.com/portal/en/community/topic/log4j-security-issue</a></strong></p>
<p><strong>Mattermost FocalBoard : <a href="https://forum.mattermost.org/t/log4j-vulnerability-concern/12676" rel="noopener">https://forum.mattermost.org/t/log4j-vulnerability-concern/12676</a></strong></p>
<p><strong>McAfee : <a href="https://kc.mcafee.com/corporate/index?page=content&amp;id=KB95091" rel="noopener">https://kc.mcafee.com/corporate/index?page=content&amp;id=KB95091</a></strong></p>
<p><strong>Metabase : <a href="https://github.com/metabase/metabase/commit/8bfce98beb25e48830ac2bfd57432301c5e3ab37" rel="noopener">https://github.com/metabase/metabase/commit/8bfce98beb25e48830ac2bfd57432301c5e3ab37</a></strong></p>
<p><strong>Microsoft : <a href="https://msrc-blog.microsoft.com/2021/12/11/microsofts-response-to-cve-2021-44228-apache-log4j2/" rel="noopener">https://msrc-blog.microsoft.com/2021/12/11/microsofts-response-to-cve-2021-44228-apache-log4j2/</a></strong></p>
<p><strong>Minecraft : <a href="https://www.minecraft.net/en-us/article/important-message--security-vulnerability-java-edition" rel="noopener">https://www.minecraft.net/en-us/article/important-message&#8211;security-vulnerability-java-edition</a></strong></p>
<p><strong>MISP : <a href="https://twitter.com/MISPProject/status/1470051242038673412" rel="noopener">https://twitter.com/MISPProject/status/1470051242038673412</a></strong></p>
<p><strong>MoogSoft : <a href="https://servicedesk.moogsoft.com/hc/en-us/articles/4412463233811?input_string=log4j+vulnerability+%7C%7C+cve-2021-44228" rel="noopener">https://servicedesk.moogsoft.com/hc/en-us/articles/4412463233811?input_string=log4j+vulnerability+%7C%7C+cve-2021-44228</a></strong></p>
<p><strong>Mulesoft : <a href="https://help.mulesoft.com/s/article/Apache-Log4j2-vulnerability-December-2021" rel="noopener">https://help.mulesoft.com/s/article/Apache-Log4j2-vulnerability-December-2021</a></strong></p>
<h3><strong>N</strong></h3>
<p><strong>N-able : <a href="https://www.n-able.com/security-and-privacy/apache-log4j-vulnerability" rel="noopener">https://www.n-able.com/security-and-privacy/apache-log4j-vulnerability</a></strong></p>
<p><strong>NELSON : <a href="https://github.com/getnelson/nelson/blob/f4d3dd1f1d4f8dfef02487f67aefb9c60ab48bf5/project/custom.scala" rel="noopener">https://github.com/getnelson/nelson/blob/f4d3dd1f1d4f8dfef02487f67aefb9c60ab48bf5/project/custom.scala</a></strong></p>
<p><strong>NEO4J : <a href="https://community.neo4j.com/t/log4j-cve-mitigation-for-neo4j/48856" rel="noopener">https://community.neo4j.com/t/log4j-cve-mitigation-for-neo4j/48856</a></strong></p>
<p><strong>NetApp : <a href="https://security.netapp.com/advisory/ntap-20211210-0007/" rel="noopener">https://security.netapp.com/advisory/ntap-20211210-0007/</a></strong></p>
<p><strong>Netflix : <a href="https://github.com/search?q=org%3ANetflix+CVE-2021-44228&amp;type=commits" rel="noopener">https://github.com/search?q=org%3ANetflix+CVE-2021-44228&amp;type=commits</a></strong></p>
<p><strong>NextGen Healthcare Mirth : <a href="https://github.com/nextgenhealthcare/connect/discussions/4892#discussioncomment-1789526" rel="noopener">https://github.com/nextgenhealthcare/connect/discussions/4892#discussioncomment-1789526</a></strong></p>
<p><strong>Newrelic : <a href="https://discuss.newrelic.com/t/log4j-zero-day-vulnerability-and-the-new-relic-java-agent/170322" rel="noopener">https://discuss.newrelic.com/t/log4j-zero-day-vulnerability-and-the-new-relic-java-agent/170322</a></strong></p>
<p><strong>Nutanix : <a href="https://download.nutanix.com/alerts/Security_Advisory_0023.pdf" rel="noopener">https://download.nutanix.com/alerts/Security_Advisory_0023.pdf</a></strong></p>
<h3><strong>O</strong></h3>
<p><strong>Okta : <a href="https://sec.okta.com/articles/2021/12/log4shell" rel="noopener">https://sec.okta.com/articles/2021/12/log4shell</a></strong></p>
<p><strong>Opengear : <a href="https://opengear.zendesk.com/hc/en-us/articles/4412713339419-CVE-2021-44228-aka-Log4Shell-Opengear-products-are-not-affected" rel="noopener">https://opengear.zendesk.com/hc/en-us/articles/4412713339419-CVE-2021-44228-aka-Log4Shell-Opengear-products-are-not-affected</a></strong></p>
<p><strong>OpenHab : <a href="https://github.com/openhab/openhab-distro/pull/1343" rel="noopener">https://github.com/openhab/openhab-distro/pull/1343</a></strong></p>
<p><strong>OpenNMS : <a href="https://www.opennms.com/en/blog/2021-12-10-opennms-products-affected-by-apache-log4j-vulnerability-cve-2021-44228/" rel="noopener">https://www.opennms.com/en/blog/2021-12-10-opennms-products-affected-by-apache-log4j-vulnerability-cve-2021-44228/</a></strong></p>
<p><strong>OpenMRS TALK : <a href="https://talk.openmrs.org/t/urgent-security-advisory-2021-12-11-re-apache-log4j-2/35341" rel="noopener">https://talk.openmrs.org/t/urgent-security-advisory-2021-12-11-re-apache-log4j-2/35341</a></strong></p>
<p><strong>OpenSearch : <a href="https://discuss.opendistrocommunity.dev/t/log4j-patch-for-cve-2021-44228/7950" rel="noopener">https://discuss.opendistrocommunity.dev/t/log4j-patch-for-cve-2021-44228/7950</a></strong></p>
<p><strong>Oracle : <a href="https://www.oracle.com/security-alerts/alert-cve-2021-44228.html" rel="noopener">https://www.oracle.com/security-alerts/alert-cve-2021-44228.html</a></strong></p>
<p><strong>OxygenXML : <a href="https://www.oxygenxml.com/security/advisory/CVE-2021-44228.html" rel="noopener">https://www.oxygenxml.com/security/advisory/CVE-2021-44228.html</a></strong></p>
<h3><strong>P</strong></h3>
<p><strong>Palo-Alto Networks : <a href="https://security.paloaltonetworks.com/CVE-2021-44228" rel="noopener">https://security.paloaltonetworks.com/CVE-2021-44228</a></strong></p>
<p><strong>PaperCut : <a href="https://www.papercut.com/support/known-issues/#PO-684" rel="noopener">https://www.papercut.com/support/known-issues/#PO-684</a></strong></p>
<p><strong>Parse.ly : <a href="https://blog.parse.ly/parse-ly-log4shell/" rel="noopener">https://blog.parse.ly/parse-ly-log4shell/</a></strong></p>
<p><strong>Pega : <a href="https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability" rel="noopener">https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability</a></strong></p>
<p><strong>Phenix Id : <a href="https://support.phenixid.se/uncategorized/log4j-fix/" rel="noopener">https://support.phenixid.se/uncategorized/log4j-fix/</a></strong></p>
<p><strong>PingIdentity : <a href="https://support.pingidentity.com/s/article/Log4j2-vulnerability-CVE-CVE-2021-44228" rel="noopener">https://support.pingidentity.com/s/article/Log4j2-vulnerability-CVE-CVE-2021-44228</a></strong></p>
<p><strong>Plesk : <a href="https://support.plesk.com/hc/en-us/articles/4412182812818-CVE-2021-44228-vulnerability-in-log4j-package-of-Apache" rel="noopener">https://support.plesk.com/hc/en-us/articles/4412182812818-CVE-2021-44228-vulnerability-in-log4j-package-of-Apache</a></strong></p>
<p><strong>Positive Technologies : <a href="https://twitter.com/ptsecurity/status/1469398376978522116" rel="noopener">https://twitter.com/ptsecurity/status/1469398376978522116</a></strong></p>
<p><strong>Progress / IpSwitch : <a href="https://www.progress.com/security" rel="noopener">https://www.progress.com/security</a></strong></p>
<p><strong>ProofPoint : <a href="https://proofpointcommunities.force.com/community/s/article/Proofpoint-Statement-Regarding-CVE-2021-44228-Java-logging-package-log4j2" rel="noopener">https://proofpointcommunities.force.com/community/s/article/Proofpoint-Statement-Regarding-CVE-2021-44228-Java-logging-package-log4j2</a></strong></p>
<p><strong>PTV Group : <a href="https://company.ptvgroup.com/en/resources/service-support/log4j-latest-information" rel="noopener">https://company.ptvgroup.com/en/resources/service-support/log4j-latest-information</a></strong></p>
<p><strong>Pulse Secure : <a href="https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44933/?kA13Z000000L3dR" rel="noopener">https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44933/?kA13Z000000L3dR</a></strong></p>
<p><strong>Puppet : <a href="https://puppet.com/blog/puppet-response-to-remote-code-execution-vulnerability-cve-2021-44228/" rel="noopener">https://puppet.com/blog/puppet-response-to-remote-code-execution-vulnerability-cve-2021-44228/</a></strong></p>
<p><strong>Pure Storage : <a href="https://support.purestorage.com/Field_Bulletins/Interim_Security_Advisory_Regarding_CVE-2021-44228_(%22log4j%22)" rel="noopener">https://support.purestorage.com/Field_Bulletins/Interim_Security_Advisory_Regarding_CVE-2021-44228_(%22log4j%22)</a></strong></p>
<h3><strong>Q</strong></h3>
<p><strong>Qlik : <a href="https://community.qlik.com/t5/Support-Updates-Blog/Vulnerability-Testing-Apache-Log4j-reference-CVE-2021-44228-also/ba-p/1869368" rel="noopener">https://community.qlik.com/t5/Support-Updates-Blog/Vulnerability-Testing-Apache-Log4j-reference-CVE-2021-44228-also/ba-p/1869368</a></strong></p>
<p><strong>Quest KACE : <a href="https://support.quest.com/kace-systems-management-appliance/kb/335869/is-the-kace-sma-affected-by-cve-2021-44228" rel="noopener">https://support.quest.com/kace-systems-management-appliance/kb/335869/is-the-kace-sma-affected-by-cve-2021-44228</a></strong></p>
<h3><strong>R</strong></h3>
<p><strong>Radware : <a href="https://support.radware.com/app/answers/answer_view/a_id/1029752" rel="noopener">https://support.radware.com/app/answers/answer_view/a_id/1029752</a></strong></p>
<p><strong>Red5Pro : <a href="https://www.red5pro.com/blog/red5-marked-safe-from-log4j-and-log4j2-zero-day/" rel="noopener">https://www.red5pro.com/blog/red5-marked-safe-from-log4j-and-log4j2-zero-day/</a></strong></p>
<p><strong>RedHat : <a href="https://access.redhat.com/security/cve/cve-2021-44228" rel="noopener">https://access.redhat.com/security/cve/cve-2021-44228</a></strong></p>
<p><strong>Revenera / Flexera : <a href="https://community.flexera.com/t5/Revenera-Company-News/Security-Advisory-Log4j-Java-Vulnerability-CVE-2021-44228/ba-p/216905" rel="noopener">https://community.flexera.com/t5/Revenera-Company-News/Security-Advisory-Log4j-Java-Vulnerability-CVE-2021-44228/ba-p/216905</a></strong></p>
<p><strong>Riverbed : <a href="https://supportkb.riverbed.com/support/index?page=content&amp;id=S35645" rel="noopener">https://supportkb.riverbed.com/support/index?page=content&amp;id=S35645</a></strong></p>
<p><strong>Roset.com : <a href="https://support.rosette.com/hc/en-us/articles/4416216525965-Log4j-Vulnerability" rel="noopener">https://support.rosette.com/hc/en-us/articles/4416216525965-Log4j-Vulnerability</a></strong></p>
<p><strong>RunDeck by PagerDuty : <a href="https://docs.rundeck.com/docs/history/CVEs/" rel="noopener">https://docs.rundeck.com/docs/history/CVEs/</a></strong></p>
<p><strong>RSA : <a href="https://community.rsa.com/t5/general-security-advisories-and/rsa-customer-advisory-apache-vulnerability-log4j2-cve-2021-44228/ta-p/660501" rel="noopener">https://community.rsa.com/t5/general-security-advisories-and/rsa-customer-advisory-apache-vulnerability-log4j2-cve-2021-44228/ta-p/660501</a></strong></p>
<p><strong>Rubrik : <a href="https://support.rubrik.com/s/announcementdetail?Id=a406f000001PwOcAAK" rel="noopener">https://support.rubrik.com/s/announcementdetail?Id=a406f000001PwOcAAK</a></strong></p>
<h3><strong>S</strong></h3>
<p><strong>SAFE FME Server : <a href="https://community.safe.com/s/article/Is-FME-Server-Affected-by-the-Security-Vulnerability-Reported-Against-log4j" rel="noopener">https://community.safe.com/s/article/Is-FME-Server-Affected-by-the-Security-Vulnerability-Reported-Against-log4j</a></strong></p>
<p><strong>SailPoint : <a href="https://community.sailpoint.com/t5/IdentityIQ-Blog/IdentityIQ-log4j-Remote-Code-Execution-Vulnerability/ba-p/206681" rel="noopener">https://community.sailpoint.com/t5/IdentityIQ-Blog/IdentityIQ-log4j-Remote-Code-Execution-Vulnerability/ba-p/206681</a></strong></p>
<p><strong>Salesforce : <a href="https://help.salesforce.com/s/articleView?id=000363736&amp;type=1" rel="noopener">https://help.salesforce.com/s/articleView?id=000363736&amp;type=1</a></strong></p>
<p><strong>SAP BusinessObjects : <a href="https://launchpad.support.sap.com/#/notes/3129956" rel="noopener">https://launchpad.support.sap.com/#/notes/3129956</a></strong></p>
<p><strong>SAP Global coverage : <a href="https://support.sap.com/content/dam/support/en_us/library/ssp/my-support/trust-center/sap-tc-01-5025.pdf" rel="noopener">https://support.sap.com/content/dam/support/en_us/library/ssp/my-support/trust-center/sap-tc-01-5025.pdf</a></strong></p>
<p><strong>SAS : <a href="https://support.sas.com/content/support/en/security-bulletins/remote-code-execution-vulnerability-cve-2021-44228.html" rel="noopener">https://support.sas.com/content/support/en/security-bulletins/remote-code-execution-vulnerability-cve-2021-44228.html</a></strong></p>
<p><strong>SDL worldServer : <a href="https://gateway.sdl.com/apex/communityknowledge?articleName=000017707" rel="noopener">https://gateway.sdl.com/apex/communityknowledge?articleName=000017707</a></strong></p>
<p><strong>Seafile : <a href="https://forum.seafile.com/t/urgent-zero-day-exploit-in-log4j/15575" rel="noopener">https://forum.seafile.com/t/urgent-zero-day-exploit-in-log4j/15575</a></strong></p>
<p><strong>Security Onion : <a href="https://blog.securityonion.net/2021/12/security-onion-2390-20211210-hotfix-now.html" rel="noopener">https://blog.securityonion.net/2021/12/security-onion-2390-20211210-hotfix-now.html</a></strong></p>
<p><strong>ServiceNow : <a href="https://support.servicenow.com/kb?id=kb_article_view&amp;sysparm_article=KB1000959" rel="noopener">https://support.servicenow.com/kb?id=kb_article_view&amp;sysparm_article=KB1000959</a></strong></p>
<p><strong>Sesam Info : <a href="https://twitter.com/sesam_info/status/1469711992122486791" rel="noopener">https://twitter.com/sesam_info/status/1469711992122486791</a></strong></p>
<p><strong>Shibboleth : <a href="http://shibboleth.net/pipermail/announce/2021-December/000253.html" rel="noopener">http://shibboleth.net/pipermail/announce/2021-December/000253.html</a></strong></p>
<p><strong>Siemens : <a href="https://cert-portal.siemens.com/productcert/pdf/ssa-661247.pdf" rel="noopener">https://cert-portal.siemens.com/productcert/pdf/ssa-661247.pdf</a></strong></p>
<p><strong>Signald : <a href="https://gitlab.com/signald/signald/-/issues/259" rel="noopener">https://gitlab.com/signald/signald/-/issues/259</a></strong></p>
<p><strong>Skillable : <a href="https://skillable.com/log4shell/" rel="noopener">https://skillable.com/log4shell/</a></strong></p>
<p><strong>SLF4J : <a href="http://slf4j.org/log4shell.html" rel="noopener">http://slf4j.org/log4shell.html</a></strong></p>
<p><strong>SmileCDR : <a href="https://www.smilecdr.com/our-blog/a-statement-on-log4shell-cve-2021-44228" rel="noopener">https://www.smilecdr.com/our-blog/a-statement-on-log4shell-cve-2021-44228</a></strong></p>
<p><strong>Software AG : <a href="https://tech.forums.softwareag.com/t/log4j-zero-day-vulnerability/253849" rel="noopener">https://tech.forums.softwareag.com/t/log4j-zero-day-vulnerability/253849</a></strong></p>
<p><strong>SolarWinds : <a href="https://www.solarwinds.com/trust-center/security-advisories/cve-2021-44228" rel="noopener">https://www.solarwinds.com/trust-center/security-advisories/cve-2021-44228</a></strong></p>
<p><strong>SonarSource : <a href="https://community.sonarsource.com/t/sonarqube-and-the-log4j-vulnerability/54721" rel="noopener">https://community.sonarsource.com/t/sonarqube-and-the-log4j-vulnerability/54721</a></strong></p>
<p><strong>Sonatype : <a href="https://blog.sonatype.com/a-new-0-day-log4j-vulnerability-discovered-in-the-wild" rel="noopener">https://blog.sonatype.com/a-new-0-day-log4j-vulnerability-discovered-in-the-wild</a></strong></p>
<p><strong>SonicWall : <a href="https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0032" rel="noopener">https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0032</a></strong></p>
<p><strong>Sophos : <a href="https://www.sophos.com/en-us/security-advisories/sophos-sa-20211210-log4j-rce" rel="noopener">https://www.sophos.com/en-us/security-advisories/sophos-sa-20211210-log4j-rce</a></strong></p>
<p><strong>Splunk : <a href="https://www.splunk.com/en_us/blog/bulletins/splunk-security-advisory-for-apache-log4j-cve-2021-44228.html" rel="noopener">https://www.splunk.com/en_us/blog/bulletins/splunk-security-advisory-for-apache-log4j-cve-2021-44228.html</a></strong></p>
<p><strong>Spring Boot : <a href="https://spring.io/blog/2021/12/10/log4j2-vulnerability-and-spring-boot" rel="noopener">https://spring.io/blog/2021/12/10/log4j2-vulnerability-and-spring-boot</a></strong></p>
<p><strong>SumoLogic : <a href="https://help.sumologic.com/Release-Notes/Collector-Release-Notes#december-11-2021-19-361-12" rel="noopener">https://help.sumologic.com/Release-Notes/Collector-Release-Notes#december-11-2021-19-361-12</a></strong></p>
<p><strong>SUSE : <a href="https://www.suse.com/c/suse-statement-on-log4j-log4shell-cve-2021-44228-vulnerability/" rel="noopener">https://www.suse.com/c/suse-statement-on-log4j-log4shell-cve-2021-44228-vulnerability/</a></strong></p>
<p><strong>Sterling Order IBM : <a href="https://www.ibm.com/support/pages/node/6525544" rel="noopener">https://www.ibm.com/support/pages/node/6525544</a></strong></p>
<p><strong>Sweepwidget : <a href="https://sweepwidget.com/view/23032-v9f40ns1/4zow83-23032" rel="noopener">https://sweepwidget.com/view/23032-v9f40ns1/4zow83-23032</a></strong></p>
<p><strong>Swingset : <a href="https://github.com/bpangburn/swingset/blob/017452b2d0d8370871f43a68043dacf53af7f759/swingset/CHANGELOG.txt#L10" rel="noopener">https://github.com/bpangburn/swingset/blob/017452b2d0d8370871f43a68043dacf53af7f759/swingset/CHANGELOG.txt#L10</a></strong></p>
<p><strong>Synopsys : <a href="https://community.synopsys.com/s/article/SIG-Security-Advisory-for-Apache-Log4J2-CVE-2021-44228" rel="noopener">https://community.synopsys.com/s/article/SIG-Security-Advisory-for-Apache-Log4J2-CVE-2021-44228</a></strong></p>
<p><strong>SysAid : <a href="https://www.sysaid.com/lp/important-update-regarding-apache-log4j" rel="noopener">https://www.sysaid.com/lp/important-update-regarding-apache-log4j</a></strong></p>
<p><strong>Sysdig : <a href="https://sysdig.com/blog/cve-critical-vulnerability-log4j/" rel="noopener">https://sysdig.com/blog/cve-critical-vulnerability-log4j/</a></strong></p>
<h3><strong>T</strong></h3>
<p><strong>Talend : <a href="https://jira.talendforge.org/browse/TCOMP-2054" rel="noopener">https://jira.talendforge.org/browse/TCOMP-2054</a></strong></p>
<p><strong>TealiumIQ : <a href="https://community.tealiumiq.com/t5/Announcements-Blog/Update-on-Log4j-Security-Vulnerability/ba-p/36824" rel="noopener">https://community.tealiumiq.com/t5/Announcements-Blog/Update-on-Log4j-Security-Vulnerability/ba-p/36824</a></strong></p>
<p><strong>Threema UNOFICIAL : <a href="https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592#gistcomment-3993316" rel="noopener">https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592#gistcomment-3993316</a></strong></p>
<p><strong>TrendMicro : <a href="https://success.trendmicro.com/solution/000289940" rel="noopener">https://success.trendmicro.com/solution/000289940</a></strong></p>
<p><strong>Tricentis Tosca : <a href="https://support-hub.tricentis.com/open?number=NEW0001148&amp;id=post" rel="noopener">https://support-hub.tricentis.com/open?number=NEW0001148&amp;id=post</a></strong></p>
<h3><strong>U</strong></h3>
<p><strong>Ubiquiti-UniFi-UI : <a href="https://community.ui.com/releases/UniFi-Network-Application-6-5-54/d717f241-48bb-4979-8b10-99db36ddabe1" rel="noopener">https://community.ui.com/releases/UniFi-Network-Application-6-5-54/d717f241-48bb-4979-8b10-99db36ddabe1</a></strong></p>
<p><strong>Ubuntu : <a href="https://ubuntu.com/security/CVE-2021-44228" rel="noopener">https://ubuntu.com/security/CVE-2021-44228</a></strong></p>
<p><strong>USSIGNAL MSP : <a href="https://ussignal.com/blog/apache-log4j-vulnerability" rel="noopener">https://ussignal.com/blog/apache-log4j-vulnerability</a></strong></p>
<h3><strong>V</strong></h3>
<p><strong>VArmour : <a href="https://support.varmour.com/hc/en-us/articles/4416396248717-Log4j2-Emergency-Configuration-Change-for-Critical-Auth-Free-Code-Execution-in-Logging-Utility" rel="noopener">https://support.varmour.com/hc/en-us/articles/4416396248717-Log4j2-Emergency-Configuration-Change-for-Critical-Auth-Free-Code-Execution-in-Logging-Utility</a></strong></p>
<p><strong>Varonis : <a href="https://help.varonis.com/s/article/Apache-Log4j-Zero-Day-Vulnerability-CVE-2021-44228" rel="noopener">https://help.varonis.com/s/article/Apache-Log4j-Zero-Day-Vulnerability-CVE-2021-44228</a></strong></p>
<p><strong>Veritas NetBackup : <a href="https://www.veritas.com/content/support/en_US/article.100052058" rel="noopener">https://www.veritas.com/content/support/en_US/article.100052058</a></strong></p>
<p><strong>Veeam : <a href="https://www.veeam.com/kb4254" rel="noopener">https://www.veeam.com/kb4254</a></strong></p>
<p><strong>Vespa ENGINE : <a href="https://github.com/vespa-engine/blog/blob/f281ce4399ed3e97b4fed32fcc36f9ba4b17b1e2/_posts/2021-12-10-log4j-vulnerability.md" rel="noopener">https://github.com/vespa-engine/blog/blob/f281ce4399ed3e97b4fed32fcc36f9ba4b17b1e2/_posts/2021-12-10-log4j-vulnerability.md</a></strong></p>
<p><strong>VMware : <a href="https://www.vmware.com/security/advisories/VMSA-2021-0028.html" rel="noopener">https://www.vmware.com/security/advisories/VMSA-2021-0028.html</a></strong></p>
<h3><strong>W</strong></h3>
<p><strong>Wallarm : <a href="https://lab.wallarm.com/cve-2021-44228-mitigation-update/" rel="noopener">https://lab.wallarm.com/cve-2021-44228-mitigation-update/</a></strong></p>
<p><strong>WatchGuard / Secplicity / <a href="https://www.secplicity.org/2021/12/10/critical-rce-vulnerability-in-log4js/" rel="noopener">https://www.secplicity.org/2021/12/10/critical-rce-vulnerability-in-log4js/</a></strong></p>
<p><strong>WildFlyAS : <a href="https://twitter.com/WildFlyAS/status/1469362190536818688" rel="noopener">https://twitter.com/WildFlyAS/status/1469362190536818688</a></strong></p>
<p><strong>WitFoo : <a href="https://www.witfoo.com/blog/emergency-update-for-cve-2021-44228-log4j/" rel="noopener">https://www.witfoo.com/blog/emergency-update-for-cve-2021-44228-log4j/</a></strong></p>
<p><strong>Wodby Cloud : <a href="https://twitter.com/wodbycloud/status/1470125735914450950" rel="noopener">https://twitter.com/wodbycloud/status/1470125735914450950</a></strong></p>
<p><strong>Wowza : <a href="https://www.wowza.com/docs/known-issues-with-wowza-streaming-engine#log4j2-cve" rel="noopener">https://www.wowza.com/docs/known-issues-with-wowza-streaming-engine#log4j2-cve</a></strong></p>
<p><strong>WSO2 : <a href="https://github.com/wso2/security-tools/pull/169" rel="noopener">https://github.com/wso2/security-tools/pull/169</a></strong></p>
<h3><strong>X</strong></h3>
<p><strong>XCP-ng : <a href="https://xcp-ng.org/forum/topic/5315/log4j-vulnerability-impact" rel="noopener">https://xcp-ng.org/forum/topic/5315/log4j-vulnerability-impact</a></strong></p>
<h3><strong>Y</strong></h3>
<p><strong>Yandex-Cloud : <a href="https://github.com/yandex-cloud/docs/blob/6ff6c676787756e7dd6101c53b051e4cd04b3e85/ru/overview/security-bulletins/index.md#10122021--cve-2021-44228--%D1%83%D0%B4%D0%B0%D0%BB%D0%B5%D0%BD%D0%BD%D0%BE%D0%B5-%D0%B2%D1%8B%D0%BF%D0%BE%D0%BB%D0%BD%D0%B5%D0%BD%D0%B8%D0%B5-%D0%BA%D0%BE%D0%B4%D0%B0-log4shell-apache-log4j" rel="noopener">https://github.com/yandex-cloud/docs/blob/6ff6c676787756e7dd6101c53b051e4cd04b3e85/ru/overview/security-bulletins/index.md#10122021&#8211;cve-2021-44228&#8211;%D1%83%D0%B4%D0%B0%D0%BB%D0%B5%D0%BD%D0%BD%D0%BE%D0%B5-%D0%B2%D1%8B%D0%BF%D0%BE%D0%BB%D0%BD%D0%B5%D0%BD%D0%B8%D0%B5-%D0%BA%D0%BE%D0%B4%D0%B0-log4shell-apache-log4j</a></strong></p>
<h3><strong>Z</strong></h3>
<p><strong>ZAMMAD : <a href="https://community.zammad.org/t/cve-2021-44228-elasticsearch-users-be-aware/8256" rel="noopener">https://community.zammad.org/t/cve-2021-44228-elasticsearch-users-be-aware/8256</a></strong></p>
<p><strong>Zaproxy : <a href="https://www.zaproxy.org/blog/2021-12-10-zap-and-log4shell/" rel="noopener">https://www.zaproxy.org/blog/2021-12-10-zap-and-log4shell/</a></strong></p>
<p><strong>Zerto : <a href="https://help.zerto.com/kb/000004822" rel="noopener">https://help.zerto.com/kb/000004822</a></strong></p>
<p><strong>Zesty : <a href="https://www.zesty.io/mindshare/company-announcements/log4j-exploit/" rel="noopener">https://www.zesty.io/mindshare/company-announcements/log4j-exploit/</a></strong></p>
<p><strong>Zimbra : <a href="https://forums.zimbra.org/viewtopic.php?f=15&amp;t=70240" rel="noopener">https://forums.zimbra.org/viewtopic.php?f=15&amp;t=70240</a></strong></p>
<p><strong>ZSCALER : <a href="https://www.zscaler.fr/blogs/security-research/security-advisory-log4j-0-day-remote-code-execution-vulnerability-cve-2021" rel="noopener">https://www.zscaler.fr/blogs/security-research/security-advisory-log4j-0-day-remote-code-execution-vulnerability-cve-2021</a></strong></p>
]]></content:encoded>
					
					<wfw:commentRss>https://anonyviet.com/cach-sua-loi-bao-mat-log4j-neu-ban-khong-the-update-len-ban-moi-nhat/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Hướng dẫn cài đặt NextCloud trên máy tính</title>
		<link>https://anonyviet.com/huong-dan-cai-dat-nextcloud-tren-may-tinh/</link>
					<comments>https://anonyviet.com/huong-dan-cai-dat-nextcloud-tren-may-tinh/#respond</comments>
		
		<dc:creator><![CDATA[Wdchocopie]]></dc:creator>
		<pubDate>Mon, 09 Aug 2021 11:20:01 +0000</pubDate>
				<category><![CDATA[Mạng cơ bản]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[NextCloud]]></category>
		<category><![CDATA[Raspberry Pi]]></category>
		<category><![CDATA[ubuntu]]></category>
		<guid isPermaLink="false">https://anonyviet.com/?p=32140</guid>

					<description><![CDATA[NextCloud là phần mềm giúp bạn tạo ra dịch vụ lưu trữ đám mây riêng cho cá nhân. Tức là dữ liệu sẽ lưu trên máy tính/Server riêng của bạn. Bạn sẽ tự cài đặt, phân quyền, tạo user và có cả App để cài trên điện thoại. NextCloud rất thích hợp nếu bạn muốn [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><strong>NextCloud là phần mềm giúp bạn tạo ra dịch vụ lưu trữ đám mây riêng cho cá nhân. Tức là dữ liệu sẽ lưu trên máy tính/Server riêng của bạn. Bạn sẽ tự cài đặt, phân quyền, tạo user và có cả App để cài trên điện thoại. NextCloud rất thích hợp nếu bạn muốn truy cập dữ liệu của mình từ xa hoặc công ty muốn tạo Cloud Storage để nhân viên sử dụng.</strong></p>
<p>Hôm nay, mình sẽ hướng dẫn mọi người cách cài đặt NextCloud trên Raspberry Pi nhé. Tất nhiên là bạn cũng có thể cài NextCloud trên máy tính cá nhân của mình.</p>
<h3>NextCloud là gì?</h3>
<p>NextCloud là 1 dạng của Client-Server-Sofware để tạo dịch vụ lưu trữ đám mây. Đây là 1 trong những phần mềm mở cho phép người dùng thay đổi Sourcecode và cho phép người dùng tạo 1 Server của riêng họ</p>
<p>NextCloud có giao diện dễ sử dụng với mọi người, thân thiện với nhiều loại thiết bị và họ đã cung cấp thêm các phiên bản client dành cho Window, Android hay thậm chí là IOS.</p>
<h3>Chuẩn bị</h3>
<ul>
<li>Một máy tính <strong>hoặc</strong> VPS <strong>hoặc</strong> Raspberry Pi đã cài sẵn hệ điều hành (mình sử dụng Raspberry Pi 4GB Ram &#8211; Thẻ nhớ microSD 32GB và chạy Ubuntu Server 20.04 LTS)</li>
<li>Mạng (đã mở port 443 và port 80)</li>
<li>Đã login vào user <code>root</code> (có thể xem hướng dẫn <a href="https://anonyviet.com/cach-dang-nhap-tai-khoan-root-trong-kali-linux/">tại đây</a>)</li>
<li>Khuyến khích sử dụng SSH để kết nối</li>
</ul>
<h3>Những thứ chúng ta sẽ cài:</h3>
<ul>
<li>Apache</li>
<li>PHP 7.4.1</li>
<li>MySQL</li>
<li>NextCloud</li>
</ul>
<h3>Hướng dẫn cài Apache</h3>
<p><strong>Bước 1</strong>: Cài đặt Apache</p>
<p><code>sudo apt install apache2 -y </code></p>
<p><strong>Bước 2</strong>: Start và Enable Apache</p>
<p><code>sudo systemctl start apache2</code><br />
<code>sudo systemctl enable apache2</code></p>
<p><strong>Bước 3</strong>: Kiểm tra Firewall bằng lệnh ufw</p>
<p><code>sudo ufw app list</code></p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/c-3.jpg" alt="list ufw đang chạy" width="335" height="109" title="Hướng dẫn cài đặt NextCloud trên máy tính 18"></p>
<p>Nó hiện vậy là ok nhé</p>
<p><strong>Bước 4</strong>: Cho phép traffic trên port 80 và 443</p>
<p><code>sudo ufw app info "Apache Full"</code></p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/d-2.jpg" alt="cho traffic chạy qua cổng 80 và 443" width="576" height="136" title="Hướng dẫn cài đặt NextCloud trên máy tính 19"></p>
<p>Nó hiện vậy là được nhé</p>
<p>Hãy kiểm tra xem server đã lên chưa nhé</p>
<p>Vì địa chỉ IPv4 của raspberry pi của mình là 192.168.1.5 nên mình sẽ thử vào xem</p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/download.jpg" alt="Apache HTML" width="248" height="203" title="Hướng dẫn cài đặt NextCloud trên máy tính 20"></p>
<p>Nó hiện vậy tức là Apache đã hoạt động rồi đó</p>
<h3>Cài đặt và config MySQL</h3>
<p><strong>Bước 1</strong>: Cài đặt MySQL</p>
<p><code>sudo apt install mysql-server -y</code><code> </code></p>
<p><strong>Bước 2</strong>: Cài đặt mật khẩu root cho MySQL</p>
<p><code>sudo mysql_secure_installation</code></p>
<p>Mặc đinh mật khẩu root của mysql sẽ để trống. Bước này có thể có hoặc không có tùy nhu cầu của Administrators</p>
<p><strong>Bước 3</strong>: Cài đặt cấu hình cho NextCloud</p>
<p><code>mysql -u root</code></p>
<p><strong>Tạo database và user</strong></p>
<p><code>CREATE DATABASE nextcloud;</code><br />
<code>CREATE USER 'nc_user'@'localhost' IDENTIFIED BY 'YOUR_PASSWORD_HERE';</code><br />
<code>GRANT ALL PRIVILEGES ON nextcloud.* TO 'nc_user'@'localhost';</code><br />
<code>FLUSH PRIVILEGES;</code><br />
<code>exit</code></p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/g-1-1.jpg" alt="cài đặt user cho Database" width="638" height="386" title="Hướng dẫn cài đặt NextCloud trên máy tính 21"></p>
<p><strong>Lưu ý</strong>: thay YOUR_PASSWORD_HERE thành pass của mình nhé!</p>
<h3>Cài đặt PHP</h3>
<p><code>sudo apt install -y php libapache2-mod-php php-ldap php-mysql php-cli php-bz2 php-curl php-gd php-imagick php-intl php-mbstring php-xml php-zip</code></p>
<h3>Cài đặt NextCloud</h3>
<p><strong>Bước 1</strong>: Cài đặt NextCloud</p>
<p><code>wget https://download.nextcloud.com/server/releases/nextcloud-22.1.0.zip -O /opt/nextcloud.zip</code></p>
<p><strong>Lưu ý</strong>: tại thời điểm ra bài này, NextCloud bản mới nhất là 22.1.0 nhé! đối với các bạn xem sau ngày 8/8/2021, check phiên bản mới <a href="https://nextcloud.com/fr_FR/install/#instructions-server" target="_blank" rel="noopener">tại đây</a></p>
<p><strong>Bước 2</strong>: Giải nén tệp tin đó</p>
<p><code>apt-get install unzip -y </code><br />
<code>unzip /opt/nextcloud.zip -d /var/www/</code><br />
<code>rm -f /opt/nextcloud.zip</code></p>
<p><strong>Bước 3</strong>: Nhập cấu hình Virtual Host</p>
<p><code>cat &lt;&lt; EOF &gt;&gt; /etc/apache2/sites-available/nextcloud.conf</code></p>
<p><code>&lt;VirtualHost *:80&gt;</code><br />
<code>ServerAdmin admin@localhost.local</code><br />
<code>DocumentRoot /var/www/nextcloud/</code><br />
<code>#ServerName example.com</code><br />
<code>#ServerAlias www.example.com</code></p>
<p><code>Alias /nextcloud "/var/www/nextcloud/"</code></p>
<p><code>&lt;Directory /var/www/nextcloud/&gt;</code><br />
<code>Options +FollowSymlinks</code><br />
<code>AllowOverride All</code><br />
<code>Require all granted</code><br />
<code>&lt;IfModule mod_dav.c&gt;</code><br />
<code>Dav off</code><br />
<code>&lt;/IfModule&gt;</code><br />
<code>SetEnv HOME /var/www/nextcloud</code><br />
<code>SetEnv HTTP_HOME /var/www/nextcloud</code><br />
<code>&lt;/Directory&gt;</code></p>
<p><code>ErrorLog ${APACHE_LOG_DIR}/error.log</code><br />
<code>CustomLog ${APACHE_LOG_DIR}/access.log combined</code></p>
<p><code>&lt;/VirtualHost&gt;</code><br />
<code>EOF</code></p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/l-2.jpg" alt="Nhập cấu hình Virtual Host" width="637" height="386" title="Hướng dẫn cài đặt NextCloud trên máy tính 22"></p>
<p><strong>Bước 4</strong>: Phân quyền cho NextCloud</p>
<p><code>chmod 755 -R /var/www/nextcloud/</code><br />
<code>chown www-data. -R /var/www/nextcloud/</code></p>
<p><strong>Bước 5</strong>: Bật lại các mode hỗ trợ NextCloud</p>
<p><code>sudo a2enmod rewrite</code><br />
<code>sudo a2enmod headers</code><br />
<code>sudo a2enmod env</code><br />
<code>sudo a2enmod dir</code><br />
<code>sudo a2enmod mime</code></p>
<p><strong>Bước 6</strong>: Bật Config của NextCloud và Restart Apache</p>
<p><code>sudo a2ensite nextcloud.conf</code><br />
<code>sudo systemctl reload apache2</code></p>
<p>&nbsp;</p>
<p><strong>Bước 7</strong>: Truy cập vào trang dựa vào địa chỉ ip của raspberry pi. Của mình là 192.168.1.5</p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/u.jpg" alt="Tạo NextCloud admin account" width="897" height="447" title="Hướng dẫn cài đặt NextCloud trên máy tính 23"></p>
<ul>
<li><strong>user</strong> : nc_admin</li>
<li><strong>pass</strong> : pass bạn tự đặt</li>
</ul>
<p>Kết nối với database lúc trước tạo.</p>
<ul>
<li>nc_user</li>
<li>Mật khẩu database mà bạn lập ở bước 3 phần tạo mySQL</li>
<li>nextcloud</li>
<li>localhost</li>
</ul>
<p>Và sau đó click finish Set Up</p>
<p>Đợi một lúc để quá trình cài đặt hoàn tất.</p>
<p>Giao diện sau khi cài đặt như sau:</p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/p.jpg" alt="NextCloud" width="896" height="428" title="Hướng dẫn cài đặt NextCloud trên máy tính 24"></p>
<p><img decoding="async" class="alignnone size-full " src="https://anonyviet.com/wp-content/uploads/2021/08/q.jpg" alt="NextCloud" width="894" height="434" title="Hướng dẫn cài đặt NextCloud trên máy tính 25"></p>
<p><img decoding="async" class="alignnone size-full " src="https://anonyviet.com/wp-content/uploads/2021/08/r.jpg" alt="NextCloud" width="899" height="449" title="Hướng dẫn cài đặt NextCloud trên máy tính 26"></p>
<h3>Hướng dẫn mở port modem nhà mạng</h3>
<p><strong>Bước 1</strong>: Vào địa chỉ sau: 192.168.1.1</p>
<p><strong>Bước 2</strong>: Các bạn login vào nhé. Cái này thường là của nhà mạng cung cấp. Đối với modem của VNPT, họ thường để username và password như sau:</p>
<ul>
<li>Username: admin</li>
<li>Password: Passwd2@</li>
</ul>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/1-2.jpg" alt="cổng mạng VNPT" width="349" height="404" title="Hướng dẫn cài đặt NextCloud trên máy tính 27"></p>
<p><strong>Bước 3</strong>: Trên thanh trên cùng, chọn Advance Setup -&gt; NAT. Sau khi xong, các bạn chọn Interface là wan1 xong đó chọn Virtual Server</p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/2-3.jpg" alt="Hướng dẫn NAT port" width="586" height="200" title="Hướng dẫn cài đặt NextCloud trên máy tính 28"></p>
<p><strong>Bước 4</strong>: Các bạn điền như sau nhé <img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/4-1.jpg" alt="Local IP của Raspberry PI" width="713" height="57" title="Hướng dẫn cài đặt NextCloud trên máy tính 29"> <img decoding="async" class="aligncenter  size-full" src="https://anonyviet.com/wp-content/uploads/2021/08/3-2.jpg" alt="cài đặt cho virtual server" width="523" height="457" title="Hướng dẫn cài đặt NextCloud trên máy tính 30"></p>
<p><strong>Chú thích:</strong></p>
<ul>
<li>Index: số thứ tự (khi bạn mở các port khác nhau thì cần đổi index cho mỗi port)</li>
<li>Application: Tên để các bạn dễ nhận diện</li>
<li>Protocol: Giao thức. Cái này các bạn cứ để all cho mình</li>
<li>Start Port và End Port: các bạn để 2 cái: 80 và 443</li>
<li>Phần Local ip adress, các bạn có thể tìm qua status -&gt; DHCP Client</li>
</ul>
<p><strong>Bước 5</strong>: Các bạn nhấn Apply nhé</p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/6-1.jpg" alt="Nút Apply" width="484" height="125" title="Hướng dẫn cài đặt NextCloud trên máy tính 31"></p>
<p>Các bạn có thể Check Port <a href="https://ping.eu/port-chk/" target="_blank" rel="noopener">tại đây</a></p>
<p><img decoding="async" class="size-full  aligncenter" src="https://anonyviet.com/wp-content/uploads/2021/08/7-1.jpg" alt="Check port" width="528" height="128" title="Hướng dẫn cài đặt NextCloud trên máy tính 32"></p>
<p>Tiếp theo bạn cần trỏ Domain về IP của Modem Internet nhà bạn, làm tương tự <a href="https://anonyviet.com/tao-domain-mien-phi-1-nam-bang-freenom-moi-nhat/">hướng dẫn trỏ domain từ freenom về cloudflare</a>.</p>
<p><strong>Vậy là mình vừa hướng dẫn xong các bạn cài đặt NextCloud trên Raspberry Pi. Các bạn thấy thế nào? Hãy để lại bình luận để mình biết nhé</strong></p>
<h2>Câu hỏi thường gặp</h2>
<h3>NextCloud có an toàn không?</h3>
<p>Dữ liệu của bạn được lưu trữ trên máy tính hoặc server riêng của bạn, tăng cường bảo mật so với các dịch vụ lưu trữ đám mây công cộng. Tuy nhiên, bạn vẫn cần đảm bảo máy chủ của bạn được bảo mật tốt bằng cách cập nhật phần mềm và sử dụng mật khẩu mạnh.</p>
<h3>Tôi cần những kiến thức kỹ thuật nào để cài đặt NextCloud?</h3>
<p>Bạn cần có kiến thức cơ bản về dòng lệnh và quản lý server. Bài viết hướng dẫn cài đặt trên Raspberry Pi, nhưng bạn cũng có thể áp dụng tương tự trên máy tính cá nhân hoặc VPS.  Việc cài đặt đòi hỏi một số bước kỹ thuật, tuy nhiên, hướng dẫn đã được cung cấp chi tiết trong bài viết.</p>
<h3>Tôi có thể sử dụng NextCloud trên nhiều thiết bị không?</h3>
<p>Có, NextCloud cung cấp các ứng dụng dành cho nhiều hệ điều hành như Windows, Android và iOS, cho phép bạn truy cập dữ liệu từ nhiều thiết bị khác nhau.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://anonyviet.com/huong-dan-cai-dat-nextcloud-tren-may-tinh/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Chống DDOS khi bị tấn công bằng Proxy</title>
		<link>https://anonyviet.com/1958-2/</link>
					<comments>https://anonyviet.com/1958-2/#comments</comments>
		
		<dc:creator><![CDATA[AnonyViet]]></dc:creator>
		<pubDate>Wed, 15 Jun 2016 03:05:53 +0000</pubDate>
				<category><![CDATA[DDOS]]></category>
		<category><![CDATA[anti ddos]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[chống ddos]]></category>
		<category><![CDATA[Nginx]]></category>
		<guid isPermaLink="false">http://anonyviet.com/?p=1958</guid>

					<description><![CDATA[Gần đây nổi lên 1 số script chế lại từ các đoạn code share trên mạng dùng để tấn công từ chối dịch vụ, những đoạn script chế lại này thường được attacker chỉnh sửa để sử dụng 1 danh sách proxies để flood vì vậy rất khó để limit request/connection, khi log ra thì [&#8230;]]]></description>
										<content:encoded><![CDATA[<p style="text-align: justify;">Gần đây nổi lên 1 số script chế lại từ các đoạn code share trên mạng dùng để tấn công từ chối dịch vụ, những đoạn script chế lại này thường được attacker chỉnh sửa để sử dụng 1 danh sách proxies để flood vì vậy rất khó để limit request/connection, khi log ra thì thấy có 1 số lượng lớn truy cập từ rất rất nhiều các IP khác nhau.</p>
<p style="text-align: justify;">Tuy nhiên vì ở đây attacker sử dụng proxies miễn phí nên đều có 1 điểm chung là &#8220;X_Forwarded_For&#8221;. Dạng tấn công này nếu đánh vào 1 máy chủ cấu hình cao thì thường làm overload dịch vụ bên trong như Database (Mysql) hay CGI (PHP, Perl, Websocket, &#8230;) gây ra lỗi &#8220;Time out&#8221; do phải sử lý quá nhiều request 1 lúc.</p>
<p style="text-align: justify;"><img decoding="async" class="alignnone size-full " src="https://anonyviet.com/wp-content/uploads/2017/01/bao-ve-vps-khoi-tan-cong-ddos-flood-2.jpg" width="851" height="443" alt="bao-ve-vps-khoi-tan-cong-ddos-flood-2" title="Chống DDOS khi bị tấn công bằng Proxy 34"></p>
<p style="text-align: justify;">Đoạn cấu hình dưới đây sẽ giúp bạn trong những trường hợp như vậy, nó chặn toàn bộ các request có chứa X-Forwarded_For để không làm ảnh hưởng đến các dịch vụ phía sau. Tuy nhiên nó cũng còn tùy thuộc vào Webserver bạn sử dụng và cấu hình server, nếu webserver như apache xử lý chậm gây tắc nghẽn và treo thì các bạn nên dựng nginx đứng trước để chặn.</p>
<p><span style="color: #0000ff;"><strong>Dành cho Server sử dụng Apache:</strong></span></p>
<p>Thêm đoạn code dưới đây vào file .htaccess</p>
<p>/share/anti_dos_through_multi_proxies</p>
<pre class="lang:default decode:true"># .htaccess for apache
&lt;IfModule mod_rewrite.c&gt;
RewriteEngine on
RewriteCond %{HTTP:VIA} !^$ [OR]
RewriteCond %{HTTP:FORWARDED} !^$ [OR]
RewriteCond %{HTTP:USERAGENT_VIA} !^$ [OR]
RewriteCond %{HTTP:X_FORWARDED_FOR} !^$ [OR]
RewriteCond %{HTTP:PROXY_CONNECTION} !^$ [OR]
RewriteCond %{HTTP:XPROXY_CONNECTION} !^$ [OR]
RewriteCond %{HTTP:HTTP_PC_REMOTE_ADDR} !^$ [OR]
RewriteCond %{HTTP:XROXY_CONNECTION} !^$ [OR]
RewriteCond %{HTTP:X-FORWARDED-FOR} !^$ [OR]
RewriteCond %{HTTP:HTTP_CLIENT_IP} !^$ [OR]
RewriteCond %{HTTP:FORWARDED-FOR} !^$ [OR]
RewriteCond %{HTTP:X-FORWARDED} !^$
RewriteRule ^(.*)$ - [F]
&lt;/IfModule&gt;</pre>
<div class="text_exposed_show">
<p><span style="color: #0000ff;"><strong>Dành cho Server sử dụng Nginx:</strong></span></p>
<pre class="lang:default decode:true"># nginx config
if ($http_x_forwarded_for) {return 444;}</pre>
<p>&nbsp;</p>
</div>
]]></content:encoded>
					
					<wfw:commentRss>https://anonyviet.com/1958-2/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Ngăn chặn website khác leech link ảnh từ Hosting của bạn</title>
		<link>https://anonyviet.com/ngan-chan-website-khac-leech-link-anh-tu-hosting-cua-ban/</link>
		
		<dc:creator><![CDATA[AnonyViet]]></dc:creator>
		<pubDate>Mon, 21 Dec 2015 14:36:03 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[leech]]></category>
		<guid isPermaLink="false">http://anonyviet.com/?p=852</guid>

					<description><![CDATA[Website của bạn lưu trữ và sử dụng rất nhiều hình ảnh trong các bài viết. Và một số website khác copy các bài viết từ website của bạn, sử dụng link (hot link) của các bức ảnh đó. Điều này khiến bạn tiêu tốn rất nhiều băng thông hàng tháng, và hạn chế tốc [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Website của bạn lưu trữ và sử dụng rất nhiều hình ảnh trong các bài viết. Và một số website khác copy các bài viết từ website của bạn, sử dụng link (hot link) của các bức ảnh đó. Điều này khiến bạn tiêu tốn rất nhiều băng thông hàng tháng, và hạn chế tốc độ của website bạn. Vậy làm sao để ngăn cản việc &#8220;leech link&#8221; này?. Có rất nhiều cách để chặn lấy link trong trường hợp trên: bạn có thể sử dụng file .htacess hoặc cấu hình lại file httpd.conf bằng cách thêm các dòng code bên dưới đây vào.<span id="more-852"></span></p>
<p>(Tìm hiểu .htaccess là gì, một số lệnh cơ bản htaccess <a href="https://anonyviet.com/chong-ddos-va-bao-mat-hosting-bang-htaccess/" target="_blank">xem tại đây</a>)</p>
<p>Chú ý: Mod Rewrite của Apache cần được bật nhé.<br />
Bạn tiến hành mở file httpd.conf hoặc file .htaccess trên server/hosting.</p>
<div>
<div id="highlighter_990678" class="syntaxhighlighter bash">
<div class="toolbar">
<pre class="lang:default decode:true"># vi httpd.conf</pre>
<p>Thêm đoạn mã này vào:</p>
</div>
</div>
</div>
<div>
<div class="line number1 index0 alt2">
<pre class="lang:default decode:true">SetEnvIfNoCase Referer "^https://anonyviet.com/" banimages=1
SetEnvIfNoCase Referer "^https://anonyviet.com/" banimages=1
SetEnvIfNoCase Referer "^$" banimages=1
  Order Allow,Deny
  Allow from env=banimages=1</pre>
<p>&nbsp;</p>
</div>
</div>
<p>hoặc bạn cũng có thể sử dụng một đoạn mã đơn giản khác:</p>
<div>
<div id="highlighter_8677" class="syntaxhighlighter bash">
<div class="toolbar">
<pre class="lang:default decode:true ">RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www.)?anonyviet.com/.*$ [NC]
RewriteRule ^.*.(bmp|tif|gif|jpg|jpeg|jpe|png)$ - [F]</pre>
<p>&nbsp;</p>
</div>
</div>
</div>
<p>Tips: Thông thường, nhằm mục đích quảng bá, ngoài việc ngăn chặn việc &#8220;leech link&#8221; ảnh từ hosting của bạn. Bạn có thể chuyển hình ảnh được &#8220;leech&#8221; qua một bức ảnh mà bạn tùy chọn (như logo, banner của site bạn chẳn hạn).<br />
Để làm được điều này, bạn sử dụng đoạn mã sau:</p>
<div>
<pre class="lang:default decode:true ">RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www.)?anonyviet.com/.*$ [NC]
RewriteRule .*.(gif|jpe?g|png)$ http://www.anonyviet.com/logo.jpg [R,NC,L]</pre>
<p>&nbsp;</p>
</div>
<p>Ở đoạn mã ví dụ trên mình sử dụng link là tên miền của blog mình. Hãy thay đổi bằng tên miền của website bạn!</p>
<p>Nếu bạn thêm nội dung trên vào file httpd.conf thì bạn cần restart lại apache nhé (sửa file .htaccess thì ko cần)</p>
<p>&nbsp;</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
