Pattern for string header is too loose
Issue ID: response-header-string-loosepattern
Average severity: Medium
Description
The pattern for a string header is too loosely defined. It does not actually limit what can be included in the response header.
For more details, see the OpenAPI Specification.
Example
The following is an example of how this type of risk could look in your API definition. The defined pattern is so loose that the response header can effectively include any string of any size and value:
{
"responses": {
"200": {
"description": "OK",
"headers": {
"x-ids": {
"type": "string",
"pattern": ".*"
}
}
}
}
}Possible exploit scenario
Your API has been designed to return specific data. If you define too loose pattern for strings, you do not actually limit what can be included in response headers.
Attackers typically want to make the API to change its behavior and return different data than it is supposed to. A particular API failure might leak some other data, such as records or stack trace.
Locking down the pattern of strings in your response headers helps reduce this risk.
Remediation
Set a well-defined regular expression that matches your requirements in the pattern field of the string header. This ensures that only strings matching the pattern can be included in the response header.
For example, the API below only accepts UUIDs that are compliant with RFC 4122:
{
"responses": {
"200": {
"description": "OK",
"headers": {
"x-ids": {
"type": "string",
"pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89AB][0-9a-f]{3}-[0-9a-f]{12}$"
}
}
}
}
}We recommend that you carefully think what kind of regular expression best matches your needs. Do not simply blindly copy the pattern from the code example.
Remember to include the anchors ^ and $ in your regular expression, otherwise the overall length of the pattern could be considered infinite. If you include the anchors in the regular expression and the pattern only has fixed or constant quantifiers (like {10,64}, for example), you do not have to define the property maxLength separately for the object, as the length is fully constrained by the pattern. However, if the regular expression does not include the anchors or its quantifiers are not fixed (like in ^a.*b$), it can be considered to be just a part of a longer string and the property maxLength is required to constrain the length.
For more information on regular expressions, see the following:
- Language-agnostic information on regular expressions at Base Definitions page on regular expressions
- OWASP Validation Regex Repository
- RegExr, an online tool for building and testing regular expressions
The following are examples of regular expressions for some common elements:
| Element | Examples of regular expressions | Examples with escape |
|---|---|---|
| Alphanumeric string |
|
— |
| Base64‑encoding (for an image) |
|
^data:image\\/(?:gif|png|jpeg|bmp|webp)(?:;charset=utf-8)?;base64,(?:[A-Za-z0-9]|[+/])+={0,2}$
|
| Date and time |
|
|
| Duration |
|
^\\d+:\\d{2}:\\d{2}$
|
| Email address (common format) |
|
^([a-z0-9_\\.-]+)@([\\da-z\\.-]+)\\.([a-z\\.]{2,5})$
|
| File |
|
|
| IP address |
|
|
| Numbers |
|
|
| Password constraints |
Password that has:
|
^(?=.*[0-9])(?=.*[a-z])(?=.*[A-Z])(?=.*[*.!@$%^&(){}[]:;<>,.?/~_+-=|\\]).{10,64}$
|
| Phone number |
International phone number, country code optional: Use libraries instead or regular expressions to validate phone numbers whenever possible. |
^(?:(?:\\(?(?:00|\\+)([1-4]\\d\\d|[1-9]\\d?)\\)?)?[\\-\\.\\ \\\\\\/]?)?((?:\\(?\\d{1,}\\)?[\\-\\.\\ \\\\\\/]?){0,})(?:[\\-\\.\\ \\\\\\/]?(?:#|ext\\.?|extension|x)[\\-\\.\\ \\\\\\/]?(\\d+))?$
|
| URL/URI (with protocol optional) |
|
^(https?:\\/\\/)?(www\\.)?[-a-zA-Z0-9@:%._\\+~#=]{2,256}\\.[a-z]{2,6}\\b([-a-zA-Z0-9@:%_\\+.~#?&//=]*)$
|
| UUID |
|
— |