JON: Unapproved agents can connect using the name of an existing approved agent
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat JBoss Operations Network 2.4 | |||
| cpe:/a:redhat:jboss_operations_network:2.4 | RHSA-2012:0089 | 2012-02-01T00:00:00Z | |
| Red Hat JBoss Operations Network 3.0 | |||
| cpe:/a:redhat:jboss_operations_network:3.0 | RHSA-2012:0406 | 2012-03-20T00:00:00Z | |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2012-0091 | Red Hat JBoss Operations Network (JON) before 2.4.2 and 3.0.x before 3.0.1 does not check the JON agent key, which allows remote attackers to spoof the identity of arbitrary agents via the registered agent name. |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.182% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.