Axxonnet
Monthly
Incorrect authorization in the Health Monitoring service of AxxonSoft AxxonNet on Linux (versions before 3.28.0) lets a remote attacker who already holds a shared report token - a credential intended only for read-only report access - create, modify, or delete monitoring alerts through the monitoring API. The flaw is a scope-enforcement failure rather than an authentication bypass in the strict sense: a valid low-privilege token is a hard prerequisite (PR:L, AV:N), and the resulting impact is limited to alert integrity and availability, with no confidentiality loss and no path to code execution. Severity is medium (CVSS 4.0 base 5.3; independently assessed CVSS 3.1 5.3, S:U/C:N/I:L/A:L); there is no CISA KEV listing and no public exploit identified at time of analysis, so the practical risk is suppression or forgery of health alerts by someone who already has report-level access.
Incorrect authorization in the Health Monitoring service of AxxonSoft AxxonNet on Linux (versions before 3.28.0) lets a remote attacker who already holds a shared report token - a credential intended only for read-only report access - create, modify, or delete monitoring alerts through the monitoring API. The flaw is a scope-enforcement failure rather than an authentication bypass in the strict sense: a valid low-privilege token is a hard prerequisite (PR:L, AV:N), and the resulting impact is limited to alert integrity and availability, with no confidentiality loss and no path to code execution. Severity is medium (CVSS 4.0 base 5.3; independently assessed CVSS 3.1 5.3, S:U/C:N/I:L/A:L); there is no CISA KEV listing and no public exploit identified at time of analysis, so the practical risk is suppression or forgery of health alerts by someone who already has report-level access.