A flaw was found in Quarkus. This issue occurs when receiving a request over websocket with no role-based permission specified on the Graph…
A flaw was found in Quarkus. This issue occurs when receiving a request over websocket with no role-based permission specified on the GraphQL operation, Quarkus processes the request without authentication despite the endpoint being secured. This can allow an attacker to access information and functionality outside of normal granted API permissions.
If a web server does not fully parse requested URLs before it examines them for authorization, it may be possible for an attacker to bypass authorization protection.
https://cwe.mitre.org/data/definitions/551.html →Open in CWE collection →The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways that may produce resultant weaknesses.
https://cwe.mitre.org/data/definitions/696.html →Open in CWE collection →An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key.
https://capec.mitre.org/data/definitions/463.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| build_of_quarkus | * | Tracked |
| quarkus | * | Tracked |