Read Time:9 Second
Description
The software creates an immutable text string using string concatenation operations.
Modes of Introduction:
Related Weaknesses
Consequences
Other: Reduce Performance
Category Archives: CWE
CWE-1047 – Modules with Circular Dependencies
Read Time:12 Second
Description
The software contains modules in which one module has references that cycle back to itself, i.e., there are circular dependencies.
Modes of Introduction:
Related Weaknesses
Consequences
Other: Reduce Reliability
Potential Mitigations
CVE References
CWE-94 – Improper Control of Generation of Code (‘Code Injection’)
Read Time:3 Minute, 15 Second
Description
The software constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Modes of Introduction:
– Architecture and Design
Likelihood of Exploit: Medium
Related Weaknesses
Consequences
Access Control: Bypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access Control: Gain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity, Confidentiality, Availability: Execute Unauthorized Code or Commands
Code injection attacks can lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing. Additionally, code injection can often result in the execution of arbitrary code.
Non-Repudiation: Hide Activities
Often the actions performed by injected control code are unlogged.
Potential Mitigations
Phase: Architecture and Design
Effectiveness:
Description:
Refactor your program so that you do not have to dynamically generate code.
Phase: Architecture and Design
Effectiveness:
Description:
Phase: Implementation
Effectiveness:
Description:
Phase: Testing
Effectiveness:
Description:
Use automated static analysis tools that target this type of weakness. Many modern techniques use data flow analysis to minimize the number of false positives. This is not a perfect solution, since 100% accuracy and coverage are not feasible.
Phase: Testing
Effectiveness:
Description:
Use dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software’s operation may slow down, but it should not become unstable, crash, or generate incorrect results.
Phase: Operation
Effectiveness:
Description:
Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl’s “-T” switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
Phase: Operation
Effectiveness:
Description:
Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl’s “-T” switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
CVE References
- CVE-2008-5071
- Eval injection in PHP program.
- CVE-2002-1750
- Eval injection in Perl program.
- CVE-2008-5305
- Eval injection in Perl program using an ID that should only contain hyphens and numbers.
- CVE-2002-1752
- Direct code injection into Perl eval function.
- CVE-2002-1753
- Eval injection in Perl program.
- CVE-2005-1527
- Direct code injection into Perl eval function.
- CVE-2005-2837
- Direct code injection into Perl eval function.
- CVE-2005-1921
- MFV. code injection into PHP eval statement using nested constructs that should not be nested.
- CVE-2005-2498
- MFV. code injection into PHP eval statement using nested constructs that should not be nested.
- CVE-2005-3302
- Code injection into Python eval statement from a field in a formatted file.
- CVE-2007-1253
- Eval injection in Python program.
- CVE-2001-1471
- chain: Resultant eval injection. An invalid value prevents initialization of variables, which can be modified by attacker and later injected into PHP eval statement.
- CVE-2002-0495
- Perl code directly injected into CGI library file from parameters to another CGI program.
- CVE-2005-1876
- Direct PHP code injection into supporting template file.
- CVE-2005-1894
- Direct code injection into PHP script that can be accessed by attacker.
- CVE-2003-0395
- PHP code from User-Agent HTTP header directly inserted into log file implemented as PHP script.
CWE-940 – Improper Verification of Source of a Communication Channel
Read Time:49 Second
Description
The software establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.
When an attacker can successfully establish a communication channel from an untrusted origin, the attacker may be able to gain privileges and access unexpected functionality.
Modes of Introduction:
– Architecture and Design
Likelihood of Exploit:
Related Weaknesses
Consequences
Access Control, Other: Gain Privileges or Assume Identity, Varies by Context
An attacker can access any functionality that is inadvertently accessible to the source.
Potential Mitigations
Phase: Architecture and Design
Effectiveness:
Description:
CVE References
- CVE-2000-1218
- DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning
- CVE-2005-0877
- DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning
- CVE-2001-1452
- DNS server caches glue records received from non-delegated name servers
CWE-941 – Incorrectly Specified Destination in a Communication Channel
Read Time:31 Second
Description
The software creates a communication channel to initiate an outgoing request to an actor, but it does not correctly specify the intended destination for that actor.
Modes of Introduction:
– Architecture and Design
Likelihood of Exploit:
Related Weaknesses
Consequences
Potential Mitigations
CVE References
- CVE-2013-5211
- composite: NTP feature generates large responses (high amplification factor) with spoofed UDP source addresses.
- CVE-1999-0513
- Classic “Smurf” attack, using spoofed ICMP packets to broadcast addresses.
- CVE-1999-1379
- DNS query with spoofed source address causes more traffic to be returned to spoofed address than was sent by the attacker.
CWE-942 – Permissive Cross-domain Policy with Untrusted Domains
Read Time:2 Minute, 5 Second
Description
The software uses a cross-domain policy file that includes domains that should not be trusted.
Modes of Introduction:
– Implementation
Likelihood of Exploit:
Related Weaknesses
Consequences
Confidentiality, Integrity, Availability, Access Control: Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Read Application Data, Varies by Context
An attacker may be able to bypass the web browser’s same-origin policy. An attacker can exploit the weakness to manipulate or steal cookies, create requests that can be mistaken for those of a valid user, compromise confidential information, or execute malicious code on the end user systems for a variety of nefarious purposes. Other damaging attacks include the disclosure of end user files, installation of Trojan horse programs, redirecting the user to some other page or site, running ActiveX controls (under Microsoft Internet Explorer) from sites that a user perceives as trustworthy, and modifying presentation of content.
Potential Mitigations
Phase: Architecture and Design
Effectiveness:
Description:
Avoid using wildcards in the cross-domain policy file. Any domain matching the wildcard expression will be implicitly trusted, and can perform two-way interaction with the target server.
Phase: Architecture and Design, Operation
Effectiveness:
Description:
For Flash, modify crossdomain.xml to use meta-policy options such as ‘master-only’ or ‘none’ to reduce the possibility of an attacker planting extraneous cross-domain policy files on a server.
Phase: Architecture and Design, Operation
Effectiveness:
Description:
For Flash, modify crossdomain.xml to use meta-policy options such as ‘master-only’ or ‘none’ to reduce the possibility of an attacker planting extraneous cross-domain policy files on a server.
CVE References
- CVE-2012-2292
- Product has a Silverlight cross-domain policy that does not restrict access to another application, which allows remote attackers to bypass the Same Origin Policy.
- CVE-2014-2049
- The default Flash Cross Domain policies in a product allows remote attackers to access user files.
- CVE-2007-6243
- Chain: Adobe Flash Player does not sufficiently restrict the interpretation and usage of cross-domain policy files, which makes it easier for remote attackers to conduct cross-domain and cross-site scripting (XSS) attacks.
- CVE-2008-4822
- Chain: Adobe Flash Player and earlier does not properly interpret policy files, which allows remote attackers to bypass a non-root domain policy.
- CVE-2010-3636
- Chain: Adobe Flash Player does not properly handle unspecified encodings during the parsing of a cross-domain policy file, which allows remote web servers to bypass intended access restrictions via unknown vectors.
CWE-943 – Improper Neutralization of Special Elements in Data Query Logic
Read Time:28 Second
Description
The application generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
Modes of Introduction:
– Implementation
Likelihood of Exploit:
Related Weaknesses
Consequences
Confidentiality, Integrity, Availability, Access Control: Bypass Protection Mechanism, Read Application Data, Modify Application Data, Varies by Context
Potential Mitigations
CVE References
- CVE-2014-2503
- Injection using Documentum Query Language (DQL)
- CVE-2014-2508
- Injection using Documentum Query Language (DQL)
CWE-95 – Improper Neutralization of Directives in Dynamically Evaluated Code (‘Eval Injection’)
Read Time:1 Minute, 57 Second
Description
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. “eval”).
This may allow an attacker to execute arbitrary code, or at least modify what code can be executed.
Modes of Introduction:
– Architecture and Design
Likelihood of Exploit: Medium
Related Weaknesses
Consequences
Confidentiality: Read Files or Directories, Read Application Data
The injected code could access restricted data / files.
Access Control: Bypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access Control: Gain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity, Confidentiality, Availability, Other: Execute Unauthorized Code or Commands
Code injection attacks can lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing. Additionally, code injection can often result in the execution of arbitrary code.
Non-Repudiation: Hide Activities
Often the actions performed by injected control code are unlogged.
Potential Mitigations
Phase: Architecture and Design, Implementation
Effectiveness:
Description:
If possible, refactor your code so that it does not need to use eval() at all.
Phase: Implementation
Effectiveness:
Description:
Phase: Implementation
Effectiveness:
Description:
CVE References
- CVE-2008-5071
- Eval injection in PHP program.
- CVE-2002-1750
- Eval injection in Perl program.
- CVE-2008-5305
- Eval injection in Perl program using an ID that should only contain hyphens and numbers.
- CVE-2002-1752
- Direct code injection into Perl eval function.
- CVE-2002-1753
- Eval injection in Perl program.
- CVE-2005-1527
- Direct code injection into Perl eval function.
- CVE-2005-2837
- Direct code injection into Perl eval function.
- CVE-2005-1921
- MFV. code injection into PHP eval statement using nested constructs that should not be nested.
- CVE-2005-2498
- MFV. code injection into PHP eval statement using nested constructs that should not be nested.
- CVE-2005-3302
- Code injection into Python eval statement from a field in a formatted file.
- CVE-2007-1253
- Eval injection in Python program.
- CVE-2001-1471
- chain: Resultant eval injection. An invalid value prevents initialization of variables, which can be modified by attacker and later injected into PHP eval statement.
- CVE-2007-2713
- Chain: Execution after redirect triggers eval injection.
CWE-96 – Improper Neutralization of Directives in Statically Saved Code (‘Static Code Injection’)
Read Time:1 Minute, 23 Second
Description
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.
Modes of Introduction:
– Architecture and Design
Likelihood of Exploit:
Related Weaknesses
Consequences
Confidentiality: Read Files or Directories, Read Application Data
The injected code could access restricted data / files.
Access Control: Bypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access Control: Gain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity, Confidentiality, Availability, Other: Execute Unauthorized Code or Commands
Code injection attacks can lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing. Additionally, code injection can often result in the execution of arbitrary code.
Non-Repudiation: Hide Activities
Often the actions performed by injected control code are unlogged.
Potential Mitigations
Phase: Implementation
Effectiveness:
Description:
Phase: Implementation
Effectiveness:
Description:
Perform proper output validation and escaping to neutralize all code syntax from data written to code files.
CVE References
- CVE-2002-0495
- Perl code directly injected into CGI library file from parameters to another CGI program.
- CVE-2005-1876
- Direct PHP code injection into supporting template file.
- CVE-2005-1894
- Direct code injection into PHP script that can be accessed by attacker.
- CVE-2003-0395
- PHP code from User-Agent HTTP header directly inserted into log file implemented as PHP script.
- CVE-2007-6652
- chain: execution after redirect allows non-administrator to perform static code injection.
CWE-97 – Improper Neutralization of Server-Side Includes (SSI) Within a Web Page
Read Time:17 Second
Description
The software generates a web page, but does not neutralize or incorrectly neutralizes user-controllable input that could be interpreted as a server-side include (SSI) directive.
Modes of Introduction:
– Architecture and Design
Likelihood of Exploit:
Related Weaknesses
Consequences
Confidentiality, Integrity, Availability: Execute Unauthorized Code or Commands
Potential Mitigations
CVE References