Pyn3Rd

An incorrect authorization issue exists in the FORM authentication process. This allows the bypassing of a security constraint that restricts a user to POST access while denying GET access to a resource.

Improper access control and incorrect authorization allow an unauthenticated attacker to bypass security constraints. This occurs when a security constraint for a longer path is processed before a more restrictive constraint for a shorter sub-path, leading the system to evaluate constraints incorrectly and grant access to protected resources.

An authentication bypass exists in the DIGEST authenticator. If a client makes a DIGEST authenticated request with a `nonceCount` on the upper boundary of the replay window before `windowSize` requests are made, that request can be replayed once while the associated `nonceCount` remains within the replay window.

An off-by-one error in the rewrite valves occurs when the `[N]` flag is used. This causes the rewrite processing to restart at the second rule instead of the first rule.

An improper authorization issue exists where `security-role-ref` definitions are incorrectly used as role aliases within the Realm, in addition to their intended use with `Request.isUserInRole()`.

An issue exists in the Server: Connection Handling component. An unauthenticated attacker with network access via multiple protocols can exploit this to cause a hang or a frequently repeatable crash, resulting in a complete Denial of Service (DOS), which is a condition where the service becomes unavailable to legitimate users.

An unsafe reflection issue exists where externally-controlled input can be used to select classes or code. Specifically, a user-controlled model can load arbitrary classes, which may lead to remote code execution.

An improper neutralization of input during web page generation allows for Cross-site Scripting (XSS). The `MessageServlet` in the ActiveMQ web console API copies every JMS message property into an HTTP response header without validation. This allows an attacker to overwrite and inject security headers by setting them on JMS messages returned by the servlet.

Improper input validation and improper control of code generation lead to a code injection issue. Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at the '/api/jolokia/' endpoint on the web console. The default access policy allows execution operations on all ActiveMQ MBeans, specifically the `addNetworkConnector(String)` function within `BrokerService`. An authenticated attacker can use a crafted discovery URI to trigger the `brokerConfig` parameter of the VM transport via a "masterslave://" URL. This allows the loading of a Spring XML application context using `ResourceXmlApplicationContext`. Since this context instantiates singleton beans before the configuration is validated, arbitrary code can be executed on the broker's JVM through bean factory methods such as `Runtime.exec()`.