First published: Mon Jan 16 2012(Updated: )
If a JON agent is registered in a JON server's inventory with a given name, then any other agent can connect to the JON server and assume the identity of this registered agent simply by assuming its agent name. The JON agent key is not verified, allowing malicious JON agents to connect to the server.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat JBoss Operations Network | <=2.4.1 | |
Red Hat JBoss Operations Network | =2.0.0 | |
Red Hat JBoss Operations Network | =2.0.1 | |
Red Hat JBoss Operations Network | =2.1.0 | |
Red Hat JBoss Operations Network | =2.2 | |
Red Hat JBoss Operations Network | =2.3 | |
Red Hat JBoss Operations Network | =2.3.1 | |
Red Hat JBoss Operations Network | =2.4 | |
Red Hat JBoss Operations Network | =3.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-0052 is classified as a medium severity vulnerability due to the potential for unauthorized access to a JON server.
To fix CVE-2012-0052, update the Red Hat JBoss Operations Network to a version that is not affected by this vulnerability.
CVE-2012-0052 affects multiple versions of Red Hat JBoss Operations Network including versions from 2.0.0 to 2.4.1.
If exploited, CVE-2012-0052 allows an attacker to impersonate a registered JON agent, potentially leading to unauthorized control and data access.
There are no documented workarounds for CVE-2012-0052, and users are advised to upgrade to a secure version.