Metalikelihood: Mediumseverity: MediumStable

CAPEC-137Parameter Injection

Abstraction
Meta
Status
Stable
Likelihood
Medium
Severity
Medium

Description

An adversary manipulates the content of request parameters for the purpose of undermining the security of the target. Some parameter encodings use text characters as separators. For example, parameters in a HTTP GET message are encoded as name-value pairs separated by an ampersand (&). If an attacker can supply text strings that are used to fill in these parameters, then they can inject special characters used in the encoding scheme to add or modify parameters. For example, if user input is fed directly into an HTTP GET request and the user provides the value "myInput&new_param=myValue", then the input parameter is set to myInput, but a new parameter (new_param) is also added with a value of myValue. This can significantly change the meaning of the query that is processed by the server. Any encoding scheme where parameters are identified and separated by text characters is potentially vulnerable to this attack - the HTTP GET encoding used above is just one example.

Related weaknesses· 1

CWE-88

Exploits1

TypeTargetConfidenceTier
WeaknessImproper Neutralization of Argument Delimiters in a Command ('Argument Injection')cwe-88100%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CAPEC
HTTP Parameter Pollution (HPP)
CAPEC
Command Injection
CAPEC
XSS Through HTTP Query Strings
CAPEC
Resource Injection
CAPEC
SQL Injection through SOAP Parameter Tampering
CAPEC
SQL Injection
Sourced from MITRE CAPEC. Curated by Adam Lundqvist, SQUR.