The Stimulsoft Reports software component is vulnerable to remote code execution (RCE) by using the subreports feature. An RCE vulnerability can be used by an attacker to execute arbitrary code on the server which can be used to exfiltrate data, change or remove data as well as reduce the availability of the service. It can also be used to pivot to other resources within the environment as well as install arbitrary software.| securityblog.omegapoint.se
The requested page could not be found.| securityblog.omegapoint.se
Writeup for the potential security issue that the HAAPI authorization flow sends a valid, signed JWT token to the front end. Since these HAAPI JWT tokens are exposed in the browser, a misconfigured API, which improperly accepts Curity tokens by only validating the signature of the JWT, enables an attacker to use the leaked JWTs to gain unauthorized access to the API.| Omegapoint Security Blog
Secure architecture is a broad topic. This article highlights six important architectural decisions and patterns that fundamentally impact the overall security of this system. The article is also provides an overview and introduction to the seven part article series Defense in depth.| Omegapoint Security Blog
This document defines a set of questions Omegapoint uses for security reviews. The purpose is to be able to cover many aspects of security for a cloud-native DevOps team, during a two-hour interview with the team.| securityblog.omegapoint.se
A vulnerability in Authentik’s OAuth 2.0 implementation (CVE-2024-52289) allowed attackers to bypass redirect URI validation due to the insecure use of regular expressions. By exploiting this flaw, an attacker could redirect authentication responses to a malicious server, enabling account takeover. Authentik has addressed the issue in patched versions (2024.10.3 and 2024.8.5) by enforcing strict string matching for URI validation.| securityblog.omegapoint.se
CVE-2024-45031 in the IAM solution Apache Syncope allows a low-privileged attacker to inject an XSS payload in a self-registration/self-service portal. The payload executes in a high-privilege context of an administrative portal, enabling privilege escalation through session riding against system administrators.| Omegapoint Security Blog
Virtually all of the systems we are building today share data via public networks. We rarely want that data to be available to everyone, so we restrict access to it.| securityblog.omegapoint.se
In the previous article, we talked about what information we require to achieve strong access control. This article looks at how we transfer information on what scopes and audiences the user has approved, their identity and details on their login, plus rights we use for access control.| securityblog.omegapoint.se
In the first two articles, we discussed how to design your system in order to build strong access control. We looked at how you can strike the right balance in terms of what information is associated with your access token, and we looked at balancing identity and local permissions. This article will take a look at how to configure a client in order to get a token, and how we handle sessions.| securityblog.omegapoint.se
Our first three articles were about designing and getting an access token. We also established a model for how we move from identity and scopes to the permissions that we base all further access control on. In this article, we discuss what you need to do when implementing your API in order to protect your functions and your data.| Omegapoint Security Blog
The first three articles covered modelling identity and the steps necessary to retrieve an access token. The fourth article showed how to validate an incoming request and build a fine-grained access control for our API. In this article we will discuss the infrastructure necessary to deploy and operate the system we’ve described in the previous articles. We will also cover some important notes regarding data management.| Omegapoint Security Blog
In the previous article we covered some important security aspects regarding server-side infrastructure. This article covers some of the challenges we face on the client-side, in particular when working with browsers. The browser is a very attractive target environment for distributing applications and systems to the user. It’s easy to access and requires no additional installation since most of today’s users have access to a modern browser. For the user it is, compared to installing and ...| Omegapoint Security Blog
This article summarizes the learnings from article series and highlight key security principles and recommended further reading.| Omegapoint Security Blog
Developing systems that expose sensitive information on the internet requires us as developers and architects to think about security at all times. The classic model with only a strong perimeter defense is no longer suitable for modern architecture. As a result of this our role has changed, and we need to shoulder a larger responsibility for the security of the APIs and applications we develop. With the contents gathered on this page we describe what you need in order to build a system with s...| Omegapoint Security Blog
*** THIS VERSION HAS BEEN ARCHIVED *** It is recommended to use the latest version of the Omegapoint CIS Control Verifications for Cloud Native Applications.| Omegapoint Security Blog
This document interprets CIS Controls v8 IG 3 for a cloud-native system built, operated, and defended by a DevOps team. It references additional standards for guidance on implementation details, in example CIS Benchmarks and OWASP material.| securityblog.omegapoint.se
This blog covers several potential security issues that were identified in TruffleHog v3; an open source secret scanner. The issues were reported to Truffle Security, the team behind TruffleHog in December 2023.| securityblog.omegapoint.se
CVE-2023-6927 Keycloak vulnerability allows bypassing redirect URI validation which can be used as a vector for stealing authorization codes, access tokens and be used to redirect victims to arbitrary hosts.| securityblog.omegapoint.se
As independent security consultants we have had the opportunity and privilege to help our customers selecting and implementing a plethora of different solutions.In this article we aim to share with you some of the key factors to consider when selecting the right IdP solution for you, a central part of your architecture and IAM solution.| securityblog.omegapoint.se
This article gives an introduction to ethical hacking and web application penetration testing, and how it differs from for other types of penetration tests. We cover the basic principles of penetration testing and a simplified model for pentesting methodology. It will highlight key aspects of a high-quality security review, where the penetration test plays a big part, and the importance for developers to embrace a hacker's mindset (and vice-versa)| securityblog.omegapoint.se
This article will show how to implement our six-step model for building APIs highlighting key aspects for creating APIs that are secure by design. Example code is available on GitHub.| securityblog.omegapoint.se
This article presents a test-driven approach to application security and shows how we can write automated tests to prove that our defenses work as expected.| securityblog.omegapoint.se
In this blog, we'll dive deeply into two potential security issues that Omegapoint identified in AWS API Gateway authorizers. We reported these issues to AWS in November 2022 and January 2023. AWS rolled out mitigations to all AWS customer accounts in May 2023.| securityblog.omegapoint.se