On May 26, NGINX issued a security announcement that fixed a DNS resolver vulnerability (CVE -2021-23017) in the NGINX resolver.

ngx_resolver_copy() handles DNS responses with errors. When the "resolver" instruction is used in the NGINX configuration file, it might allow an attacker who is able to forge UDP packets from the DNS server to cause 1-byte memory overwrite, resulting in worker process crash or other potential impacts.

Vulnerability level: high risk, CVSS score 8.1

Affected versions: NGINX 0.6.18 - 1.20.0

If you want to know more details, you can visit the following link: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-23017

Two days before this security vulnerability was disclosed, on May 24, Apache released version 2.6. This version contains many excellent features, such as support for using Java to write plugins. Apache 2.6 is not affected by this vulnerability.

Apache only uses some features of NGINX, other core functions, such as:

• Route matching
• IP matching
• DNS resolve
• Dynamic Upstream
• Dynamic Certificate

are all implemented by Apache instead of the built-in mechanism of NGINX, so it will not be affected by this security vulnerability.

Apache ​

Apache is a dynamic, real-time, high-performance API gateway that provides rich traffic management features such as load balancing, dynamic upstream, canary release, service meltdown , authentication , observability and so on.

You can use Apache to handle traditional north-south traffic, as well as east-west traffic between services.

In the cloud-native era, dynamic and observability are standard features of API gateway.

This architecture of Apache can not only meet the elastic scaling and rapid release under the cloud-native architecture, but also be more efficient, flexible and secure. It also cooperates with SkyWalking deeply in observability, improving service management capability greatly.

Welcome to follow and use Apache : https://github.com/apache/