GnuTLS v3.8.13 does not properly enforce name constraints, as demonstrated by a permitted subtree violation for EE O=Evil accepted although outside permitted O=Good. NOTE: the Supplier does not consider this an actionable security vulnerability because of its threat model doesnt consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.) policy.
The product does not properly control the allocation and maintenance of a limited resource.
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.