CAPEC-12: Choosing Message Identifier

Choosing Message Identifier


Typical_Severify: High



This pattern of attack is defined by the selection of messages distributed over via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a privileged one.


PeerOf: CAPEC-21 |Exploitation of Trusted Credentials

ChildOf: CAPEC-216 |Communication Channel Manipulation

Execution Flow Attack Setp

Setp 1 Explore

Determine the nature of messages being transported as well as the identifiers to be used as part of the attack

Setp 2 Experiment

If required, authenticate to the distribution channel

Setp 3 Experiment

If any particular client's information is available through the transport means simply by selecting a particular identifier, an attacker can simply provide that particular identifier.

Setp 4 Experiment

Attackers with client access connecting to output channels could change their channel identifier and see someone else's (perhaps more privileged) data.


Information and client-sensitive (and client-specific) data must be present through a distribution channel available to all users.

Distribution means must code (through channel, message identifiers, or convention) message destination in a manner visible within the distribution means itself (such as a control channel) or in the messages themselves.


Level Low

All the attacker needs to discover is the format of the messages on the channel/distribution means and the particular identifier used within the messages.


The Attacker needs the ability to control source code or application configuration responsible for selecting which message/channel id is absorbed from the public distribution means.


Scope Impact Likelihood
C o n f i d e n t i a l i t y Read Data
Confidentiality Access Control Authorization Gain Privileges


{'p': ['Associate some ACL (in the form of a token) with an authenticated user which they provide middleware. The middleware uses this token as part of its channel/message selection for that client, or part of a discerning authorization decision for privileged channels/messages.', 'The purpose is to architect the system in a way that associates proper authentication/authorization with each channel/message.']}

Re-architect system input/output channels as appropriate to distribute self-protecting data. That is, encrypt (or otherwise protect) channels/messages so that only authorized readers can see them.


A certain B2B interface on a large application codes for messages passed over an MQSeries queue, on a single "Partners" channel. Messages on that channel code for their client destination based on a partner_ID field, held by each message. That field is a simple integer. Attackers having access to that channel, perhaps a particularly nosey partner, can simply choose to store messages of another partner's ID and read them as they desire. Note that authentication does not prevent a partner from leveraging this attack on other partners. It simply disallows Attackers without partner status from conducting this attack.


201 | 通过发送数据的信息暴露

306 | 关键功能的认证机制缺失



2014-06-23 | CAPEC Content Team | The MITRE Corporation


2015-12-07 | CAPEC Content Team | The MITRE Corporation

Updated Description Summary