With less than a week to go until Magento 1 End of Life, based on our recent eCommerce “universe” security scan, there are over 218,000 Magento 1 sites yet to migrate.
In fact, only 2,576 Magento 1 websites migrated off Magento 1 last month - the numbers are a lot lower than the payments industry leaders would be happy with.
Firstly there are not going to be any spoilers in here I am afraid; while Foregenix participates in feedback on all PCI SSC issued standards and is an active member of the Global Executive Assessor Roundtable (GEAR), we do so under non-disclosure agreement, so we will not be commenting on the draft of PCI DSS version 4.0 that we provided feedback on. PCI DSS v3.2.1 has been around for a number of years and based on the standard lifecycle will be replaced shortly.
A fair amount of the work we do in the Foregenix Penetration Testing team is, in one way or another, a flavour of web application penetration testing. In these assessments we come across command execution vulnerabilities that belong in one of two different categories:
In this blog post we will discuss the latter, cases where the output of our command is not directly displayed on the application, and present a strategy for obtaining access to the output of our command using recursive DNS queries. Finally we construct a practical example of the discussed strategy via a step by step process bypassing different constraints imposed to us by the use of DNS as an out of band retrieval method.
A great deal has been written about the Magento 1 End Of Life in June 2020 (less than 45 days time), this article will present a different perspective into the challenge.
The Payment Card Industry Security Standards Council (PCI SSC) requires organisations to determine the scope of their PCI DSS assessment accurately.
Prior to discussing data discovery, it is important to define PCI DSS assessment scoping. The official definition by the PCI SSC for scoping is:
'Process of identifying all system components, people, and processes to be included in a PCI DSS assessment'.
With less than a week to go until Magento 1 End of Life, based on our recent eCommerce “universe” security scan, there are over 218,000 Magento 1 sites yet to migrate.
In fact, only 2,576 Magento 1 websites migrated off Magento 1 last month - the numbers are a lot lower than the payments industry leaders would be happy with.
Firstly there are not going to be any spoilers in here I am afraid; while Foregenix participates in feedback on all PCI SSC issued standards and is an active member of the Global Executive Assessor Roundtable (GEAR), we do so under non-disclosure agreement, so we will not be commenting on the draft of PCI DSS version 4.0 that we provided feedback on. PCI DSS v3.2.1 has been around for a number of years and based on the standard lifecycle will be replaced shortly.
A fair amount of the work we do in the Foregenix Penetration Testing team is, in one way or another, a flavour of web application penetration testing. In these assessments we come across command execution vulnerabilities that belong in one of two different categories:
In this blog post we will discuss the latter, cases where the output of our command is not directly displayed on the application, and present a strategy for obtaining access to the output of our command using recursive DNS queries. Finally we construct a practical example of the discussed strategy via a step by step process bypassing different constraints imposed to us by the use of DNS as an out of band retrieval method.
A great deal has been written about the Magento 1 End Of Life in June 2020 (less than 45 days time), this article will present a different perspective into the challenge.
The Payment Card Industry Security Standards Council (PCI SSC) requires organisations to determine the scope of their PCI DSS assessment accurately.
Prior to discussing data discovery, it is important to define PCI DSS assessment scoping. The official definition by the PCI SSC for scoping is:
'Process of identifying all system components, people, and processes to be included in a PCI DSS assessment'.
