Avigilon ACM latest & previous releases has an "Area" bug which may be in connection with potentially a bug within Mercury Firmware itself.
Subscriber Discussion
Avigilon ACM With Mercury Firmware Latest & Previous Releases Has An "Area" Bug
U
Undisclosed #1
Jul 02, 2018Why don't these manufacturers just take their hardware to hacker cons and make it available on a publicly available network with a sign saying "feel free to hack me if you can".
Below the sign is all the information needed, kernel version, gnu lic, even admin credentials.
have an emulator that lets you terminal to the source of the pic controller and see the code?
if you really want to find out how robust your system is take to the place where you will find the anti-robust problem solvers.
most equipment already sits on a protected environment and may not always be the lowest lying fruit.
what if your hardware has the biggest mistake of all and it has just not had the chance to be exposed?
do you use pen testers? that's a good start, how about bring your equipment and post it to the live unknown pen testers at a good con? it would be nice if you had emulators so you do not end up bricking a few controllers.
1,2,3 go!
RK
Rashid Khan
Jul 03, 2018I agree but for some reason the Physical Security industry is still thinking it is very different to the IT industry even though it no longer is different. In the IT industry this practice is called Ethical Hacking and is commonplace. In the Physical Security space manufacturers are still running scared of getting their image tarnished etc.
Having said that your comment doesn't seem to respond to my actual discussion or does it?
U
Undisclosed #1
Jul 03, 2018"Area" Bug /discuss.
Did not want to respond only add my preference tag to your post.
I really don't know what Ethical hacking is? Perhaps, all hacking is ethical but it's application is used incorrectly by some. Perhaps the "IT Ethical Hackers" are simply creating a title for a very wise copy & paste industry oh look at my linkedin I just authored a technical post of CISSP security implementation.
Now back to this mercury platform....can you post any proofs of a flaw or vulnerability or is this just an extension of what you have found online and feel you need to post here?
In the past mercury has been good to me, I just never liked their PCB footprint. It takes up too much room. 12 readers on 1320s in a CTX-6 or the competitors.. 14 readers in a Netbox, 8 readers in a model-8, 12 readers um..10 readers Vertx, 16 readers G3 enclosure using AC-1s, 8 Readers Thorn Miniplex. 8 Readers ACU(amag LOL), 8 readers Pegasus, 8 readers Brivo, 14 readers PW-5000, 4 readers N-1IV, 8 readers Maxxess, I could go on but I will end with 16 readers istar ultra or 32 hardwired readers in a trove2 with another 32 IP-ACM or ASSA ABLOY..easy to fit two Trove2 enclosures on a 4x8 board for a total of 64 hard wired readers and 64 on the 485 bus or Ethernet so 128 footprint versus....well if you must still use mercury in 2018 more power to you. It is so common everyone is building off of it. Do you not see the black swan?
Mercury has a lot of good applications and is very robust, I don't hate...the PCB boards are just too....fat.
RK
Rashid Khan
Jul 04, 2018No, Hacking is not always in fact mostly un-ethical and illegal.
The Avigilon "Area" bug is definitely present and I have proof of bug admission from Avigilon themselves via email. I don't want to upload that "proof" here as Avigilon are working on a fix, if they do not come up with a fix then i might communicate that with IPVM.
The affected mercury boards are EP1501 and MR51e. However both these boards are really small & tiny & compact, so I don't know what you are talking about, your knowledge seems to be out of date.
JH
John Honovich
Jul 04, 2018Update: I forwarded this to Avigilon, Avigilon confirmed receipt and said they are looking into this. I'll update as I hear more, feel free to nudge me if you do not see a response soon.
RK
Rashid Khan
Jul 04, 2018UM
Undisclosed Manufacturer #2
Jul 09, 2018We just recently had a major issue with a client using Maxxess where the controller wouldn't update and it took awhile to figure out. They had to load a backup copy of the customer's DB and run it in the lab and then they were able to recreate it. They're fixing it with an updated software release. Wonder if it was related.
New discussion
Ask questions and get answers to your physical security questions from IPVM team members and fellow subscribers.
Newest discussions