EN · DE Request an offer
Services

Source Code Audits

Analysis of source code for security vulnerabilities.

Overview

White-box review of your code

In a white-box approach, our analysts examine source code written in C, C++, C#, Go, Java, Perl, PHP and Python. The source code analysis identifies both vulnerabilities in the code and logic errors that cause unexpected behaviour. In addition, we analyse the running application dynamically: while the static analysis examines the source code, the dynamic analysis examines the application at runtime.

The goal of a source code audit is to identify vulnerabilities and logic errors in the analysed applications. They can then be fixed or mitigated, which increases the security of the application.

Focus areas

  • Authentication and session management
  • Access control
  • Input validation and injection
  • Deserialisation and XML processing
  • Cryptography
  • Secrets in the code
  • Memory safety
  • Dependencies and frameworks
Scope

What we test

Depending on your environment and the agreed scope, we examine in particular:

What we review in the code

Authentication and Session Management

Review of login, password storage (e.g. suitable hashing methods), password reset, multi-factor authentication and the handling of sessions and tokens.

Access Control

Review of whether authorisation checks are implemented consistently and on the server side for all functions and data, so that users can only access the resources they are authorised to.

Input Validation and Injection

Examination of the processing of input and the encoding of output in order to detect vulnerabilities such as SQL, OS command, LDAP or template injection, Cross-Site Scripting (XSS), path traversal and Server-Side Request Forgery (SSRF).

Deserialisation and XML Processing

Review of the processing of serialised objects and XML data for insecure deserialisation and XML External Entities (XXE).

Cryptography

Review of the algorithms and modes used, the generation of random values and the handling of keys, as well as of the use of weak or outdated algorithms.

Secrets in the Code

Searching for passwords, API keys, tokens and private keys in the source code, in configuration files and in the version history.

Error Handling and Logging

Review of whether errors disclose sensitive information, whether sensitive data is written to logs and whether security-relevant events are logged.

File Handling

Examination of code segments that interact with files (e.g. file uploads), including the validation of file types and sizes and the secure handling of file paths.

Business Logic and Concurrency

Review of the business logic for weaknesses through which legitimate functions could be misused, and for race conditions in concurrent processing.

Memory Safety

For languages such as C and C++, review for vulnerabilities such as buffer overflows, use-after-free errors, format string vulnerabilities and integer overflows.

Dependencies and Frameworks

Identification of libraries and frameworks with known vulnerabilities, and review of whether their security functions (e.g. CSRF protection or output encoding) are used correctly.

Configuration and Deployment

On request, review of configuration files, container definitions (e.g. Dockerfiles), deployment templates and CI/CD pipelines for insecure settings.

Approach

How it works

  1. 1
    Scoping

    Objectives, rules of engagement and time frame, agreed in writing.

  2. 2
    Testing

    Hands-on testing by experienced analysts, supported by tools.

  3. 3
    Reporting

    Management summary, reproducible findings and remediation advice.

  4. 4
    Retest

    On request, we verify your fixes and update the report.

Results

What you receive

  • Management summary, understandable without prior technical knowledge
  • Overview of all findings with their risk rating
  • Technical details for each vulnerability: affected systems, evidence and specific remediation advice
  • Description of the procedure, the tools used and the rating scheme
  • Report in English or German
  • On request a retest of your fixes and an updated report
From the field

An attack path from our projects

Anonymised attack paths from our projects, step by step, and what helped against them.

Web application penetration test

From one customer account to all customer data

Starting point: a regular test account in a customer portal.

  1. Predictable IDs

    Invoices were loaded by sequential numbers.

  2. Missing access control

    The server did not check whom an invoice belonged to: other numbers returned the invoices of other customers (IDOR).

  3. Admin function

    An administrative API function only checked that a user was logged in, not their role.

  4. All customer data

    Read and write access to the data of every customer.

What helped: authorisation checks for every object and every function on the server; the retest confirmed the fixes.

FAQ

Frequently asked questions

Questions we often hear about this service.

All questions
Which programming languages do you review?

C, C++, C#, Go, Java, Perl, PHP and Python.

Do you also test the running application?

Yes. In addition to the static analysis of the source code, we analyse the running application dynamically, so that we also find vulnerabilities that only show at runtime.

Not sure where to start?

Tell us about your environment, and we will propose a scope that fits.

Talk to us
@nullseclabs

Follow us on X for more information and current topics.