Massive Afrihost security flaw exposed

I think it's a bit of a leap to make an all out character assassination here of people you don't know, or have any insight into their reasons for making the decision they make. As I mentioned, I would be happy to make an introduction if you are genuinely interested in furthering the conversation around these topics for the benefit of all.

I think you've made your point, and I think we can agree that you would have done things differently. But lets keep the personal remarks out of the conversation :)

Asking for his CV is rather condescending.
 
There is no reason they can justify the decision that was made, ever. It is also not character assassination but questioning their fitness for the role they are in based on evidence in the public domain, but I will leave all that out of it to keep things mostly civil...

At the end of the day I would suggest those responsible for your system design investigate getting CISSP certified as well as your company getting ISO27001 accredited as two good starting points...
 
There is no reason they can justify the decision that was made, ever. It is also not character assassination but questioning their fitness for the role they are in based on evidence in the public domain, but I will leave all that out of it to keep things mostly civil...

At the end of the day I would suggest those responsible for your system design investigate getting CISSP certified as well as your company getting ISO27001 accredited as two good starting points...

I won't pretend I know what those numbers mean, but I am literally pasting that into a Skype chat with our Dev manager right now.

Thanks :)
 
I won't pretend I know what those numbers mean, but I am literally pasting that into a Skype chat with our Dev manager right now.

Thanks :)

If it means your back end becomes more secure then it’s a pleasure... also investigate implementing pci-dss for your payment and payment method platform if it’s in house or require it from your 3rd party provider
 
If it means your back end becomes more secure then it’s a pleasure... also investigate implementing pci-dss for your payment and payment method platform if it’s in house or require it from your 3rd party provider

Yeah, this is where I feel like it might be more meaningful to introduce you to someone a lot smarter than me. Would love for you to drop me a mail on [email protected] and I can promise it will go straight to the top guys :)
 
Yeah, this is where I feel like it might be more meaningful to introduce you to someone a lot smarter than me. Would love for you to drop me a mail on [email protected] and I can promise it will go straight to the top guys :)

Will send an email in the morning and see what’s what and such...
 
Hey Everyone

We're aware of the article and I know that this was something we have been working on prior to Taylor Gibb's posts on Facebook.

I can't go into a in-depth discussion on a public forum, but I can say that we do have measures in place that would prevent some of the issues mentioned on this thread.

Clients can see all the numbers that connect to their DSL products. There was a feature that could flag and block unknown numbers (I haven't checked in a while). However, clients can contact us at any time and we will block any number that shouldn't be accessing their accounts from our system and investigate further.

We're actively looking into other preventative measures we can put in place.

We also don't store passwords in plain text. These are always encrypted.


a reactive measure in this instance is a bit futile is it not, by the time you ask to block something its too late.

only allow connections from registered line references, the uk did this since they started called a cbuk reference. you could hand out dsl login details for a better subscriber experience and security was not a concern.
 
https://www.iso.org/isoiec-27001-information-security.html
It's a system of standards which you apply to keep information secure :)

As a customer, I am appalled .
As a developer I am shocked at the answers I read above :(

Us MyBB reps aren't qualified software developers, so it's sometimes a bit hard for us to answer these technical questions, but we do have an open channel directly to our developers and we do our best to facilitate responses back and forth between them and our community. I can, however, say with confidence that they are definitely aware and up to standard with the most modern certifications and practices.
 
a reactive measure in this instance is a bit futile is it not, by the time you ask to block something its too late.

only allow connections from registered line references, the uk did this since they started called a cbuk reference. you could hand out dsl login details for a better subscriber experience and security was not a concern.

Great suggestion. :) The feature to lock in CLIDs in ClientZone rolled out last night. Go check it out. ;)
 
Someones account gets hacked and a few gigs are used. Big whoop.

How is this different from a router being hacked?
 
Hardly the sidelines... I work in the it industry... we would never in a million years provide a support agent the ability to see a users password regardless of the level of tech savvy of the user.

The fact that you didn’t architect your system from day one with that type of basic security is appalling in the extreme and you should question whether your security officer and your software architect are actually worth their salaries

Hold up there Kevin Mitnick. Yes, they were able to show the passwords in cleartext on a form but that is hardly the end of the world.
I'm not usually first in line to come to Afrihost's defence but the accusations you made are laughable.

Instead of trying to sound authoritative on something you really have no clue about, maybe try to look at your own systems and see where you allow decryption of supposed private information. You will probably find a lot of cases that are much, much worse than this.
 
Hold up there Kevin Mitnick. Yes, they were able to show the passwords in cleartext on a form but that is hardly the end of the world.
I'm not usually first in line to come to Afrihost's defence but the accusations you made are laughable.

Instead of trying to sound authoritative on something you really have no clue about, maybe try to look at your own systems and see where you allow decryption of supposed private information. You will probably find a lot of cases that are much, much worse than this.

*pats on the head*

They've allowed passwords to be in clear text on a form, which indicates that at best they can be decrypted from the DB on the fly, or that they're stored in cleartext.. Neither of those are acceptable basic security best practices, and you cannot claim to have the best of the best systems architects or security officers if this was allowed through the door in the first place.

I am in no doubt that there are areas on our own systems where private info is not as secure as it should be... but they are being rectified as soon as they are found and not just being put on backlogs to be dealt with at a later date.
 
*pats on the head*

They've allowed passwords to be in clear text on a form, which indicates that at best they can be decrypted from the DB on the fly, or that they're stored in cleartext.. Neither of those are acceptable basic security best practices, and you cannot claim to have the best of the best systems architects or security officers if this was allowed through the door in the first place.

I am in no doubt that there are areas on our own systems where private info is not as secure as it should be... but they are being rectified as soon as they are found and not just being put on backlogs to be dealt with at a later date.

Our passwords have always been encrypted. We have never stored passwords in plain text. :) Please check out our response to the Fin24 article here.
 
*pats on the head*

They've allowed passwords to be in clear text on a form, which indicates that at best they can be decrypted from the DB on the fly, or that they're stored in cleartext.. Neither of those are acceptable basic security best practices, and you cannot claim to have the best of the best systems architects or security officers if this was allowed through the door in the first place.

I am in no doubt that there are areas on our own systems where private info is not as secure as it should be... but they are being rectified as soon as they are found and not just being put on backlogs to be dealt with at a later date.

Now a much more interesting thing to ponder is how they manage those credit cards though.

Nowhere does Afrihost claim PCI compliance [at least not obviously on the webpage], which means if the credit card billing system is inhouse, there are some very legitimate concerns.

This password thing is ultimately trivial in comparison to credit card info.
 
Our passwords have always been encrypted. We have never stored passwords in plain text. :) Please check out our response to the Fin24 article here.

Which is why I put the caveat of either or... :) But encryption that can be decrypted on the fly like that is as bad as storing a cleartext password ultimately....

The problem for you guys, is it speaks to lax security in the systems architecture...

At the very least you are aware of it and are taking steps to rectify the issues, which is better than many companies.
 
Now a much more interesting thing to ponder is how they manage those credit cards though.

Nowhere does Afrihost claim PCI compliance [at least not obviously on the webpage], which means if the credit card billing system is inhouse, there are some very legitimate concerns.

This password thing is ultimately trivial in comparison to credit card info.

I did see the thread in the Afrihost Support forum relating to that but I decided not to comment on that... but yes, ADSL passwords are ultimately trivial in the grand scheme of things, and if they are storing CC's and the CVC's on their systems then there are clear causes for huge concern from their customers.
 
I am in no doubt that there are areas on our own systems where private info is not as secure as it should be... but they are being rectified as soon as they are found and not just being put on backlogs to be dealt with at a later date.

Pot meet kettle.
 
Top
Sign up to the MyBroadband newsletter
X