debian-mirror-gitlab/doc/development/secure_coding_guidelines.md

Security Guidelines

This document contains descriptions and guidelines for addressing security vulnerabilities commonly identified in the GitLab codebase. They are intended to help developers identify potential security vulnerabilities early, with the goal of reducing the number of vulnerabilities released over time.

Contributing

If you would like to contribute to one of the existing documents, or add guidelines for a new vulnerability type, please open an MR! Please try to include links to examples of the vulnerability found, and link to any resources used in defined mitigations. If you have questions or when ready for a review, please ping gitlab-com/gl-security/appsec.

Permissions

Description

Application permissions are used to determine who can access what and what actions they can perform. For more information about the permission model at GitLab, please see the GitLab permissions guide or the EE docs on permissions.

Impact

Improper permission handling can have significant impacts on the security of an application. Some situations may reveal sensitive data or allow a malicious actor to perform harmful actions. The overall impact depends heavily on what resources can be accessed or modified improperly.

A common vulnerability when permission checks are missing is called IDOR for Insecure Direct Object References.

When to Consider

Each time you implement a new feature/endpoint, whether it is at UI, API or GraphQL level.

Mitigations

Start by writing tests around permissions: unit and feature specs should both include tests based around permissions

• Fine-grained, nitty-gritty specs for permissions are good: it is ok to be verbose here
  • Make assertions based on the actors and objects involved: can a user or group or XYZ perform this action on this object?
  • Consider defining them upfront with stakeholders, particularly for the edge cases
• Do not forget abuse cases: write specs that make sure certain things can't happen
  • A lot of specs are making sure things do happen and coverage percentage doesn't take into account permissions as same piece of code is used.
  • Make assertions that certain actors cannot perform actions
• Naming convention to ease auditability: to be defined, e.g. a subfolder containing those specific permission tests or a #permissions block

Be careful to also test visibility levels and not only project access rights.

Some example of well implemented access controls and tests:

1. example1
2. example2
3. example3

NB: any input from development team is welcome, e.g. about rubocop rules.

Regular Expressions guidelines

Anchors / Multi line

Unlike other programming languages (e.g. Perl or Python) Regular Expressions are matching multi-line by default in Ruby. Consider the following example in Python:

import re
text = "foo\nbar"
matches = re.findall("^bar$",text)
print(matches)

The Python example will output an emtpy array ([]) as the matcher considers the whole string foo\nbar including the newline (\n). In contrast Ruby's Regular Expression engine acts differently:

text = "foo\nbar"
p text.match /^bar$/

The output of this example is #<MatchData "bar">, as Ruby treats the input text line by line. In order to match the whole string the Regex anchors \A and \z should be used according to Rubular.

Impact

This Ruby Regex speciality can have security impact, as often regular expressions are used for validations or to impose restrictions on user-input.

Examples

GitLab specific examples can be found here and there.

Another example would be this fictional Ruby On Rails controller:

class PingController < ApplicationController
  def ping
    if params[:ip] =~ /^\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}$/
      render :text => `ping -c 4 #{params[:ip]}`
    else
      render :text => "Invalid IP"
    end
  end
end

Here params[:ip] should not contain anything else but numbers and dots. However this restriction can be easily bypassed as the Regex anchors ^ and $ are being used. Ultimately this leads to a shell command injection in ping -c 4 #{params[:ip]} by using newlines in params[:ip].

Mitigation

In most cases the anchors \A for beginning of text and \z for end of text should be used instead of ^ and $.

Further Links

• Rubular is a nice online tool to fiddle with Ruby Regexps.

Server Side Request Forgery (SSRF)

Description

A Server-side Request Forgery (SSRF) is an attack in which an attacker is able coerce a application into making an outbound request to an unintended resource. This resource is usually internal. In GitLab, the connection most commonly uses HTTP, but an SSRF can be performed with any protocol, such as Redis or SSH.

With an SSRF attack, the UI may or may not show the response. The latter is called a Blind SSRF. While the impact is reduced, it can still be useful for attackers, especially for mapping internal network services as part of recon.

Impact

The impact of an SSRF can vary, depending on what the application server can communicate with, how much the attacker can control of the payload, and if the response is returned back to the attacker. Examples of impact that have been reported to GitLab include:

• Network mapping of internal services
  • This can help an attacker gather information about internal services that could be used in further attacks. More details.
• Reading internal services, including cloud service metadata.
  • The latter can be a serious problem, because an attacker can obtain keys that allow control of the victim's cloud infrastructure. (This is also a good reason to give only necessary privileges to the token.). More details.
• When combined with CRLF vulnerability, remote code execution. More details

When to Consider

• When the application makes any outbound connection

Mitigations

In order to mitigate SSRF vulnerabilities, it is necessary to validate the destination of the outgoing request, especially if it includes user-supplied information.

The preferred SSRF mitigations within GitLab are:

1. Only connect to known, trusted domains/IP addresses.
2. Use the GitLab::HTTP library
3. Implement feature-specific mitigations

GitLab HTTP Library

The GitLab::HTTP wrapper library has grown to include mitigations for all of the GitLab-known SSRF vectors. It is also configured to respect the Outbound requests options that allow instance administrators to block all internal connections, or limit the networks to which connections can be made.

In some cases, it has been possible to configure GitLab::HTTP as the HTTP connection library for 3rd-party gems. This is preferrable over re-implementing the mitigations for a new feature.

• More details

Feature-specific Mitigations

For situtions in which a whitelist or GitLab:HTTP cannot be used, it will be necessary to implement mitigations directly in the feature. It is best to validate the destination IP addresses themselves, not just domain names, as DNS can be controlled by the attacker. Below are a list of mitigations that should be implemented.

Important Note: There are many tricks to bypass common SSRF validations. If feature-specific mitigations are necessary, they should be reviewed by the AppSec team, or a developer who has worked on SSRF mitigations previously.

• Block connections to all localhost addresses
  • 127.0.0.1/8 (IPv4 - note the subnet mask)
  • ::1 (IPv6)
• Block connections to networks with private addressing (RFC 1918)
  • 10.0.0.0/8
  • 172.16.0.0/12
  • 192.168.0.0/24
• Block connections to link-local addresses (RFC 3927)
  • 169.254.0.0/16
  • In particular, for GCP: metadata.google.internal -> 169.254.169.254
• For HTTP connections: Disable redirects or validate the redirect destination
• To mitigate DNS rebinding attacks, validate and use the first IP address received

See url_blocker_spec.rb for examples of SSRF payloads

XSS guidelines

Description

Cross site scripting (XSS) is an issue where malicious JavaScript code gets injected into a trusted web application and executed in a client's browser. The input is intended to be data, but instead gets treated as code by the browser.

XSS issues are commonly classified in three categories, by their delivery method:

• Persistent XSS
• Reflected XSS
• DOM XSS

Impact

The injected client-side code is executed on the victim's browser in the context of their current session. This means the attacker could perform any same action the victim would normally be able to do through a browser. The attacker would also have the ability to:

• log victim keystrokes
• launch a network scan from the victim's browser
• potentially obtain the victim's session tokens
• perform actions that lead to data loss/theft or account takeover

Much of the impact is contingent upon the function of the application and the capabilities of the victim's session. For further impact possibilities, please check out the beef project.

When to consider?

When user submitted data is included in responses to end users, which is just about anywhere.

Mitigation

In most situations, a two-step solution can be utilized: input validation and output encoding in the appropriate context.

Input validation

• Input Validation

Setting expectations

For any and all input fields, ensure to define expectations on the type/format of input, the contents, size limits, the context in which it will be output. It's important to work with both security and product teams to determine what is considered acceptable input.

Validate input

• Treat all user input as untrusted.
• Based on the expectations you defined above:
  • Validate the input size limits.
  • Validate the input using a whitelist approach to only allow characters through which you are expecting to receive for the field.
    • Input which fails validation should be rejected, and not sanitized.

Note that blacklists should be avoided, as it is near impossible to block all variations of XSS.

Output encoding

Once you've determined when and where the user submitted data will be output, it's important to encode it based on the appropriate context. For example:

• Content placed inside HTML elements need to be HTML entity encoded.
• Content placed into a JSON response needs to be JSON encoded.
• Content placed inside HTML URL GET parameters need to be URL-encoded
• Additional contexts may require context-specific encoding.

Additional info

Mitigating XSS in Rails

• XSS Defense in Rails
• XSS Defense with HAML
• Validating Untrusted URLs in Ruby
• RoR Model Validators

GitLab specific libraries for mitigating XSS

Vue

• isSafeURL

Content Security Policy

• Content Security Policy
• Use nonce-based Content Security Policy for inline JavaScript

Free form input fields

Sanitization

• HTML Sanitization
• DOMPurify

iframe sandboxes

• iframe sandboxing

Select examples of past XSS issues affecting GitLab

• Stored XSS in user status

Developer Training

• Introduction to XSS
• Reflected XSS
• Persistent XSS
• DOM XSS
• XSS in depth
• XSS Defense
• XSS Defense in Rails
• XSS Defense with HAML
• JavaScript URLs
• URL encoding context
• Validating Untrusted URLs in Ruby
• HTML Sanitization
• DOMPurify
• Safe Client-side JSON Handling
• iframe sandboxing
• Input Validation
• Validate size limits
• RoR model validators
• Whitelist input validation
• Content Security Policy