lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <644f04a8-1efb-4966-a1e8-1b408e4b978f@cloudaware.eu> Date: Sun, 20 Oct 2024 12:37:31 +0200 From: Jeroen Hermans via Fulldisclosure <fulldisclosure@...lists.org> To: fulldisclosure@...lists.org Cc: Emiel van Berlo <emiel@...ego.nl> Subject: [FD] CVE-2024-48939: Unauthorized enabling of API in Paxton Net2 software CloudAware Security Advisory CVE-2024-48939: Unauthorized enabling of API in Paxton Net2 software ======================================================================== Summary ======================================================================== Bypass of Paxton Net2 API license. Possible leaking of PII and access to admin functionality. No physical access to computer running Paxton Net2 is required. ======================================================================== Product ======================================================================== * Paxton Net2 (version < 6.07.14023.5015 (SR4)) ======================================================================== Detailed description ======================================================================== Paxton Net2 software offers an API. This API offers the user access to sensitive data such as access logs and other user data.[2] In order to enable the API a license file is needed. The license file is trivial to generate as demonstrated in POC in ref [1]. This is possible while the signature checks in the Net2 software were not functional for the license file. Additionally to the license file user credentials are needed to authenticate against the API. The vendor has fixed this in version 6.07.14023.5015 (SR4) of the Net2 software. ======================================================================== Solution ======================================================================== Upgrade Paxton Net2 to version 6.07.14023.5015 (SR4) ======================================================================== Mitigation ======================================================================== 1) If an upgrade is not an option - as `anyone' can create valid license files; ensure that the filesystem of computers running Paxton Net2 are not reachable by unauthorised entities. 2) Evaluate the impact of the disclosure of any configurations rolled out prior to these mitigation steps ======================================================================== Weblinks ======================================================================== [1] https://github.com/gitaware/poc_exploit_paxton_license [2] https://www.paxton-access.com/integrating-with-paxton/how-to-integrate-with-net2/integration-capability-matrix/ ======================================================================== History ======================================================================== Feb 26, 2024: Paxton informed about working POC Feb 29, 2024: Paxton confirms working POC <Sept 2024: Paxton releases software update to fix issue Oct 10, 2024: CVE-2024-48939 issued Download attachment "OpenPGP_0x52DD23305307A27C.asc" of type "application/pgp-keys" (670 bytes) Download attachment "OpenPGP_signature.asc" of type "application/pgp-signature" (237 bytes) _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Powered by blists - more mailing lists