CSRF attacks are often used to compromise the data and features of a web application.
Principles, impacts, possible exploitations, we present in this article an overview of the CSRF vulnerability as well as security best practices and measures to implement to prevent the risks of attacks.
Over the years, social engineering attacks have become a reality for all companies, regardless of their sector of activity or size.
Beyond the technical vulnerabilities that are often exploited to gain unauthorised access to data and systems, the favourite entry point for attackers remains the employees of a company, most often via phishing attacks.
Network security is a major challenge for companies. Indeed, the growing importance of IT assets, the interconnection of information systems and their exposure have increased the risks of attacks. At the same time, information (data) is produced, processed, exchanged and exploited by systems and on networks that may be vulnerable in all their components or configuration: servers, workstations, segmentation, Wi-Fi, user access, applications, etc.
APIs are everywhere. In most IT systems (mobile applications, web platforms, cloud infrastructures, etc.) and in all sectors of activity, these programming interfaces facilitate the exchange of data and their availability to a wide audience, whether customers, partners, or employees. APIs are also the driving force behind the development and growth of connected objects, as they form the basis of the communication channels of IoT systems.
Another article on Node.js security? But in this one, we focus on the most common vulnerabilities encountered during penetration testing.
Node related vulnerabilities have consequences for your entire web application. It is therefore essential to detect and correct them. Some of these flaws are not specific to Node and also exist in other languages and frameworks. This is why we have focused on providing general best practices and specific tools for Node.js.
Let’s dive in.
During our security audits, we are regularly confronted with vulnerabilities that allow commands to be executed on a system. These can take various forms depending on the type of application and the functionality impacted. You will find in this article an example of a RCE vulnerability encountered during a penetration test of a web application coded in PHP.
The security of websites (e-commerce websites, corporate websites, SaaS platforms and other web applications) is a major issue for companies. Being exposed to the public, these systems are naturally prime targets for attackers, who take advantage of numerous vulnerabilities in the features and other components: servers, data, third-party components, and other critical features such as authentication, session management or access control.
In which cases can a path traversal vulnerability occur? How to detect this flaw and protect yourself from it?
This is what we will detail in this article.
Server-side template injection (SSTI) vulnerabilities tend to be less researched than other types of flaws. However, their impact is significant and often leads to remote code execution (RCE). They are therefore flaws that should not be underestimated.
In what contexts do SSTI vulnerabilities occur? How to detect them and how to prevent them?
This is what we will see in this article.
Logistics organisations are confronted to the challenge of relying on new digital solutions without compromising their security.
Facing a booming market, new technologies have indeed become a real performance lever. But their adoption brings increased cybersecurity risks with them. The concern is now to benefit from the advantages of these tools while protecting their information systems.
This is where a penetration test will help to strengthen the level of security, as it allows to verify the risk set by attackers on a given target. For a logistics company, it will assess the security of web solutions, control software, intelligent sensors, etc. against cyberattacks.
What are the priorities during a penetration test for a company in the logistics sector?
Here is an overview of cybersecurity issues we frequently encounter and that may be specific points of attention.
Providing access to the source code during a pentest has mainly advantages or disadvantages, depending on the point of view!
Here is our feedback, which relates in particular to web application pentests.
The security of web applications is a major issue for organisations. SaaS platforms, internal applications, or e-commerce websites, all these systems must be secured to counter the increasing number of attacks targeting all their functionalities and components: servers, APIs, authentication, sessions, access control, third-party components, etc.
Beyond the protection against attacks, security has also become a key factor and a differentiating asset in pre-sales processes, particularly in B2B.
We do pentests every day. (Well, 5 days a week.) Today we’re taking you behind the scenes: we’ve got a closer look at the penetration tests performed in 2020, to share with you some figures on the vulnerabilities found.
We have also identified the three most frequent vulnerabilities found during our pentests and give our insight on the presence of these flaws. Finally, we present some other observations from our penetration tests.