85a833feba
ssl_sock_add_san_ext() builds the Subject Alternative Name extension by concatenating "DNS:" + servername and passing the result to X509V3_EXT_nconf_nid(). OpenSSL's nconf parser splits the value string on commas into multiple type:value SAN entries. The SNI comes from unauthenticated TLS ClientHello data -- an attacker can embed commas and colons (e.g., "host,dns:internal.corp,ip:10.0.0.1") to inject arbitrary GENERAL_NAME entries into certificates signed by HAProxy's configured CA. This is a CA issuance-policy violation: the operator expects one certificate per SNI hostname, but an attacker can obtain certificates containing additional hostnames/IPs/emails without access to the CA private key. Fix by adding ssl_sock_sni_is_valid() that validates the SNI contains only DNS-label-legal characters (alphanumeric, hyphens, dots). The check is performed at the start of ssl_sock_do_create_cert() before any allocation. Commas, colons, spaces, and other special characters cause certificate generation to fail, preventing SAN injection while allowing all valid hostname values. Must be backported in every maintained branches. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
Please refer to the following files depending on what you're looking for:
- INSTALL for instructions on how to build and install HAProxy
- BRANCHES to understand the project's life cycle and what version to use
- LICENSE for the project's license
- CONTRIBUTING for the process to follow to submit contributions
The more detailed documentation is located into the doc/ directory:
- doc/intro.txt for a quick introduction on HAProxy
- doc/configuration.txt for the configuration's reference manual
- doc/lua.txt for the Lua's reference manual
- doc/SPOE.txt for how to use the SPOE engine
- doc/network-namespaces.txt for how to use network namespaces under Linux
- doc/management.txt for the management guide
- doc/regression-testing.txt for how to use the regression testing suite
- doc/peers.txt for the peers protocol reference
- doc/coding-style.txt for how to adopt HAProxy's coding style
- doc/internals for developer-specific documentation (not all up to date)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.