Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added exception safety and guarantees.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="f6cb216081dee35e-26a3c59a-4f264e76-a9db9df3-01c319c0994a27cddfd07c3c"><ac:parameter ac:name=""> asynchronous-safe</ac:parameter></ac:structured-macro>
*asynchronous-safe* \[[GNU Pth|AA. C References#GNU Pth]\]
A function is asynchronous-safe, or asynchronous-signal safe, if it can be called safely and without side effects from within a signal handler context. That is, it must be able to be interrupted at any point and run linearly out of sequence without causing an inconsistent state. It must also function properly when global data might itself be in an inconsistent state. Some asynchronous-safe operations are listed here:

...

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="4a046fbaa5dcfa54-14c3d3c3-4fbb4fa2-b1bf8c62-ba66d1faa5ef766ba8cdc85c"><ac:parameter ac:name=""> availability</ac:parameter></ac:structured-macro>
*availability* \[[IEEE Std 610.12 1990|AA. C References#IEEE Std 610.12 1990]\]
The degree to which a system or component is operational and accessible when required for use. Often expressed as a probability.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="61939a0048319256-9a261b3c-4d2b4bcd-89598799-13a65d462e4f1f1e9f5b46ad"><ac:parameter ac:name=""> conformingbasic exception program<safety</ac:parameter></ac:structured-macro>
*conformingbasic exception safety* \[[ISO/IEC 9899-1999Stroustrup 01|AA. C++ References#ISO/IEC 9899-1999References#Stroustrup 01]\]
Conforming programs may depend upon nonportable features of a conforming implementation.
Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="30895007-932f-44a5-b7ad-3ef70ccc4d4d"><ac:parameter ac:name=""> error tolerance</ac:parameter></ac:structured-macro>
*error tolerance* \[[IEEE Std 610.12 1990|AA. C References#IEEE Std 610.12 1990]\]
The ability of a system or component to continue normal operation despite the presence of erroneous inputs, \[[Sutter 00|AA. C++ References#Sutter 00]\]
The basic exception safety guarantee is a property of an operation such that, if the operation terminates by raising an exception, it preserves program state invariants and prevents resource leaks. See also: [exception safety|BB. Definitions#exception safety], [strong exception safety|BB. Definitions#strong exception safety], [no-throw guarantee|BB. Definitions#no-throw guarantee].

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="bf4ad10410ec7f98-ebddef98-411441a2-b48c9450-7ca491200e698e6bc99e0483"><ac:parameter ac:name=""> exploit<conforming program</ac:parameter></ac:structured-macro>
*exploitconforming* \[[Seacord 05aISO/IEC 9899-1999|AA. C References#Seacord 05References#ISO/IEC 9899-1999]\]
AnConforming exploitprograms ismay adepend pieceupon of software or technique that takes advantage nonportable features of a security vulnerability to violate an explicit or implicit [security policy|BB. Definitions#security policy].conforming implementation.

Wiki Markup
<ac:structured-macro ac:name
Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="07fd9474540e2c49-5dac6595-4c5c49e9-a7ad9196-533c2ef961eed0c7dc260a7e"><ac:parameter ac:name=""> failerror safe<tolerance</ac:parameter></ac:structured-macro>
*failerror safetolerance* \[[IEEE Std 610.12 1990|AA. C References#IEEE Std 610.12 1990]\]
PertainingThe ability toof a system or component thatto automaticallycontinue placesnormal itself in a safe operating mode inoperation despite the eventpresence of a failure; for example, a traffic light that reverts to blinking red in all directions when normal operation failserroneous inputs.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="26a10016d319922a-ea70f0a5-401740f6-8c99a23a-604d65bf3969df686d665a2c"><ac:parameter ac:name=""> failexception soft<safety</ac:parameter></ac:structured-macro>
*failexception softsafety* \[[IEEE Std 610.12 1990Stroustrup 01|AA. C++ References#IEEE Std 610.12 1990References#Stroustrup 01]\]
PertainingAn tooperation aon systeman orobject componentis that continuessaid to providebe partialexception operationalsafe capabilityif inthat theoperation eventleaves ofthe certainobject failures;in fora example,valid astate trafficwhen lightthe that continues to alternate between red and green if the yellow light failsoperation is terminated by throwing an exception. See also: [basic exception safety|BB. Definitions#basic exception safety], [strong exception safety|BB. Definitions#strong exception safety], [no-throw guarantee|BB. Definitions#no-throw guarantee].

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="448221e2ebe374e1-6513744f-4e934782-856893fa-a529fd2cde4403ab69fbaf50"><ac:parameter ac:name=""> fault tolerance<exploit</ac:parameter></ac:structured-macro>
*fault toleranceexploit* \[[IEEE Std 610.12 1990Seacord 05a|AA. C References#IEEE Std 610.12 1990References#Seacord 05]\]
TheAn abilityexploit ofis a piece of systemsoftware or component to continue normal operation despite the presence of hardware or software faultstechnique that takes advantage of a security vulnerability to violate an explicit or implicit [security policy|BB. Definitions#security policy].

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="679d64b662c66abe-d8d41c8f-47954f5c-86278bde-0476f582d2448c9fbb80b0b9"><ac:parameter ac:name=""> freestandingfail environment<safe</ac:parameter></ac:structured-macro>
*freestandingfail environmentsafe* \[[ISO/IEC 9899-1999IEEE Std 610.12 1990|AA. C References#ISO/IEC 9899-1999References#IEEE Std 610.12 1990]\]
AnPertaining environmentto ina whichsystem Cor programcomponent executionthat mayautomatically takeplaces placeitself withoutin any benefit of ana safe operating system.&nbsp; Program startup might occur at some function other than {{main()}}, complex types might not be implemented, and only certain minimal library facilities are guaranteed to be availablemode in the event of a failure; for example, a traffic light that reverts to blinking red in all directions when normal operation fails.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="adc5775e4da20468-c876a421-455f41de-91199599-f79fa99379e520d216790f69"><ac:parameter ac:name=""> hostedfail environment<soft</ac:parameter></ac:structured-macro>
*hostedfail environmentsoft* \[[ISO/IEC 9899-1999IEEE Std 610.12 1990|AA. C References#ISO/IEC 9899-1999References#IEEE Std 610.12 1990]\]
AnPertaining environmentto thata issystem not freestanding.&nbsp; Program startup occurs at {{main()}}, complex types are implemented, and all C standard library facilities are available.or component that continues to provide partial operational capability in the event of certain failures; for example, a traffic light that continues to alternate between red and green if the yellow light fails.

Wiki Markup
<ac:structured-macro ac:name="anchor" 
Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e6b04bf477a0a561-1e42569f-448a458d-8522b7a9-42e51b2d6d1b2aa8db0e7765"><ac:parameter ac:name=""> implementation<fault tolerance</ac:parameter></ac:structured-macro>
*implementationfault tolerance* \[[ISO/IEC 9899-1999IEEE Std 610.12 1990|AA. C References#ISO/IEC 9899-1999 References#IEEE Std 610.12 1990]\]
ParticularThe setability of software, running in a particularsystem translationor environmentcomponent underto particularcontinue controlnormal options,operation thatdespite performsthe translationpresence of programshardware for,or and supports execution of functions in, a particular execution environment.software faults.

unmigrated-wikiunmigrated-wiki-markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="afdf55198a95a6ff-a4664bc3-43b24f43-b247958d-e498c693e8659b08fd53a6e1"><ac:parameter ac:name=""> implementation-definedfreestanding behavior<environment</ac:parameter></ac:structured-macro>
*implementation-definedfreestanding behaviorenvironment* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
Unspecified behavior where each implementation documents how the choice is made.
Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="3dbbbbbe-cfde-456a-9cd8-ace62ae267b5"><ac:parameter ac:name=""> incomplete type</ac:parameter></ac:structured-macro>
*incomplete type* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
An incomplete type is a type that describes an identifier but lacks information needed to determine the size of the identifierAn environment in which C program execution may take place without any benefit of an operating system.&nbsp; Program startup might occur at some function other than {{main()}}, complex types might not be implemented, and only certain minimal library facilities are guaranteed to be available.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="6c766d53b18846e3-e38e7830-40dd4f94-9db78381-7725495efbc8492398f9ebb2"><ac:parameter ac:name=""> locale-specifichosted behavior<environment</ac:parameter></ac:structured-macro>
*locale-specifichosted behaviorenvironment* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
BehaviorAn environment that is depends on local conventions of nationality, culture, and language that each implementation documentsnot freestanding.&nbsp; Program startup occurs at {{main()}}, complex types are implemented, and all C standard library facilities are available.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="8ea40580f84a1969-9cac7f45-44a1410a-bbbf969c-fa3c729842ad7bce85d8969c"><ac:parameter ac:name=""> lvalue<implementation</ac:parameter></ac:structured-macro>
*lvalueimplementation* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
AnParticular set lvalueof issoftware, anrunning expressionin witha anparticular objecttranslation typeenvironment orunder anparticular incompletecontrol typeoptions, otherthat than {{void}}. The name "lvalue" comes originally from the assignment expression {{E1 = E2}}, in which the left operand {{E1}} is required to be a (modifiable) lvalue. It is perhaps better considered as representing an object "locator value".performs translation of programs for, and supports execution of functions in, a particular execution environment.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="5bb5c166-5c23-4938-9524-d1568db7f8fc"><ac:parameter
Wiki Markup
<ac:structured-macro ac:name="anchor"> ac:schema-version="1" ac:macro-id="693bdfd9-bd0f-43b9-8581-bf2877110e2d"><ac:parameter ac:name=""> mitigation<implementation-defined behavior</ac:parameter></ac:structured-macro>
*mitigationimplementation-defined behavior* \[[Seacord 05aISO/IEC 9899-1999|AA. C References#Seacord 05References#ISO/IEC 9899-1999]\]
MitigationsUnspecified arebehavior methods,where techniques,each processes,implementation tools,documents orhow runtimethe librarieschoice that can prevent or limit exploits against vulnerabilitiesis made.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e17f8f5c5105621e-88b1d8c0-473746ff-825faa38-df96e05ad729c6223fa4d0a4"><ac:parameter ac:name=""> reentrant<incomplete type</ac:parameter></ac:structured-macro>
*reentrantincomplete type* \[[Dowd 06ISO/IEC 9899-1999|AA. C References#Dowd 06References#ISO/IEC 9899-1999]\]
AAn incomplete functiontype is reentranta iftype that multipledescribes instancesan ofidentifier thebut samelacks functioninformation canneeded runto indetermine the same address space concurrently without creating the potential for inconsistent statessize of the identifier.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="24894e1d0758c625-265d5fa6-471b49dd-a0a5b4d2-d14cbd144e88083b1be003d1"><ac:parameter ac:name=""> locale-specific reliability<behavior</ac:parameter></ac:structured-macro>
*reliabilitylocale-specific behavior* \[[IEEE Std 610.12 1990ISO/IEC 9899-1999|AA. C References#IEEE Std 610.12 1990References#ISO/IEC 9899-1999]\]
TheBehavior abilitythat ofdepends aon systemlocal orconventions componentof tonationality, performculture, itsand requiredlanguage functionsthat undereach stated conditions for a specified period of timeimplementation documents.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e5cdc371be5aea1f-a3732795-4e974a96-a86c9b45-76147c9d45870224aee90ef9"><ac:parameter ac:name=""> rvalue<lvalue</ac:parameter></ac:structured-macro>
*rvaluelvalue* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
ValueAn lvalue ofis an expression.
Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="6353b154-8867-4d3e-a419-599710cc349a"><ac:parameter ac:name=""> security flaw</ac:parameter></ac:structured-macro>
*security flaw* \[[Seacord 05a|AA. C References#Seacord 05]\]
A security flaw is a software defect that poses a potential security risk with an object type or an incomplete type other than {{void}}. The name "lvalue" comes originally from the assignment expression {{E1 = E2}}, in which the left operand {{E1}} is required to be a (modifiable) lvalue. It is perhaps better considered as representing an object "locator value".

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="401a72b3f043e064-f8031269-48594680-bf359b9f-365e673f01b07fa2cade6855"><ac:parameter ac:name=""> security policy<mitigation</ac:parameter></ac:structured-macro>
*security policymitigation* \[[InternetSeacord Society 0005a|AA. C References#InternetReferences#Seacord Society 0005]\]
AMitigations setare ofmethods, rulestechniques, andprocesses, practicestools, thator specifyruntime orlibraries regulatethat howcan a systemprevent or organizationlimit providesexploits security services to protect sensitive and critical system resourcesagainst vulnerabilities.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="0b0bca358f3f082a-a286345b-4254422c-8ae5a8c8-76cda8387ed7c29057b20109"><ac:parameter ac:name=""> sequenceno-throw point<guarantee</ac:parameter></ac:structured-macro>
*sequenceno-throw pointguarantee* C99 \[[ISO/IEC 9899-1999Stroustrup 01|AA. C++ References#ISO/IEC 9899-1999References#Stroustrup 01]\]
Evaluation of an expression may produce side effects. At specific points in the execution sequence called _sequence points_, all side effects of previous evaluations have completed, and no side effects of subsequent evaluations have yet taken place.

Wiki Markup
The following sequence points are defined by C99 \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]:

  • the call to a function, after the arguments have been evaluated
  • the end of the first operand of the following operators: && (logical AND); || (logical OR); ? (conditional); , (comma operator)
  • the end of a full declarator
  • the end of a full expression: an initializer; the expression in an expression statement (that is, at the semicolon); the controlling expression of a selection statement (if or switch); the controlling expression of a while or do statement; each of the expressions of a for statement; the expression in a return statement
  • immediately before a function returns
  • after the actions associated with each formatted input/output function conversion specifier
  • immediately before and immediately after each call to a comparison function, by a standard searching or sorting function, and between any call to a comparison function and any movement of the objects passed as arguments to that call

, \[[Sutter 00|AA. C++ References#Sutter 00]\]
The no-throw guarantee is a property of an operation such that, in addition to satisfying the [strong exception safety|BB. Definitions#strong exception safety] guarantee, it is guaranteed to complete successfully without raising or propagating an exception. See also: [exception safety|BB. Definitions#exception safety], [basic exception safety|BB. Definitions#basic exception safety], [strong exception safety|BB. Definitions#strong exception safety].

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="076670ab-b7de-4d97-abb2-9c185d8cc44d"><ac:parameter ac:name=""> reentrant</ac:parameter></ac:structured-macro>
*reentrant* \[[Dowd 06|AA. C References#Dowd 06]\]
A function is reentrant if multiple instances of the same function can run in the same address space concurrently without creating the potential for inconsistent states.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="370ebe63-1f10-4a06-9cee-c138b8bce272"><ac:parameter ac:name=""> reliability</ac:parameter></ac:structured-macro>
*reliability* \[[IEEE Std 610.12 1990|AA. C References#IEEE Std 610.12 1990]\]
The ability of a system or component to perform its required functions under stated conditions for a specified period of time.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="ef6f1dbe-58cf-4113-a611-aa6a460d751a"><ac:parameter ac:name=""> rvalue</ac:parameter></ac:structured-macro>
*rvalue* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
Value of an expression.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="39feee76-df2f-4d66-a602-212c5ef79c77"><ac:parameter ac:name=""> security flaw</ac:parameter></ac:structured-macro>
*security flaw* \[[Seacord 05a|AA. C References#Seacord 05]\]
A security flaw is a software defect that poses a potential security risk.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="60b2b904-08b8-4755-b858-54b55b28fcac"><ac:parameter ac:name=""> security policy</ac:parameter></ac:structured-macro>
*security policy* \[[Internet Society 00|AA. C References#Internet Society 00]\]
A set of rules and practices that specify or regulate how a system or organization provides security services to protect sensitive and critical system resources.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="9370a7a4-ec16-40b3-9c13-c10542e4d022"><ac:parameter ac:name=""> sequence point</ac:parameter></ac:structured-macro>
*sequence point* C99 \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
Evaluation of an expression may produce side effects. At specific points in the execution sequence called _sequence points_, all side effects of previous evaluations have completed, and no side effects of subsequent evaluations have yet taken place.

Wiki Markup
The following sequence points are defined by C99 \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]:

  • the call to a function, after the arguments have been evaluated
  • the end of the first operand of the following operators: && (logical AND); || (logical OR); ? (conditional); , (comma operator)
  • the end of a full declarator
  • the end of a full expression: an initializer; the expression in an expression statement (that is, at the semicolon); the controlling expression of a selection statement (if or switch); the controlling expression of a while or do statement; each of the expressions of a for statement; the expression in a return statement
  • immediately before a function returns
  • after the actions associated with each formatted input/output function conversion specifier
  • immediately before and immediately after each call to a comparison function, by a standard searching or sorting function, and between any call to a comparison function and any movement of the objects passed as arguments to that call

Note that not all instances of a comma in C code denote a usage of the comma operator. For example, the comma between arguments in a function call is not a sequence point.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="1d7d0649-0784-419e-a48b-bc437cfe92c8"><ac:parameter ac:name=""> strictly conforming</ac:parameter></ac:structured-macro>
*strictly conforming* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
A strictly conforming program is one that uses only those features of the language and library specified in the international standard.  Strictly conforming programs are intended to be maximally portable among conforming implementations and can't, for example, depend upon implementation-defined behavior
Note that not all instances of a comma in C code denote a usage of the comma operator. For example, the comma between arguments in a function call is not a sequence point
.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="9fb1e5e166cab526-5e47df9b-4c494c89-875f8e38-cf9bf69e24728725a7cc9316"><ac:parameter ac:name=""> strong strictlyexception conforming<safety</ac:parameter></ac:structured-macro>
*strictly conforming**strong exception safety* \[[Stroustrup 01|AA. C++ References#Stroustrup 01]\], \[[ISO/IEC 9899-1999Sutter 00|AA. C++ References#ISO/IEC 9899-1999References#Sutter 00]\]
AThe strong strictlyexception conformingsafety programguarantee is one that uses only those features of the language and library specified in the international standard.  Strictly conforming programs are intended to be maximally portable among conforming implementations and can't, for example, depend upon implementation-defined behavior a property of an operation such that, in addition to satisfying the [basic exception safety|BB. Definitions#basic exception safety] guarantee, if the operation terminates by raising an exception it has no observable effects on program state. See also: [exception safety|BB. Definitions#exception safety], [basic exception safety|BB. Definitions#basic exception safety], [no-throw guarantee|BB. Definitions#no-throw guarantee].

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="9471a37ac2c7e355-daa14bb1-4b634fc2-a14d84b4-34875d968a1c485554a3116e"><ac:parameter ac:name=""> undefined behavior</ac:parameter></ac:structured-macro>
*undefined behavior* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
Behavior, upon use of a nonportable or erroneous program construct or of erroneous data, for which the standard imposes no requirements.  An example of undefined behavior is the behavior on integer overflow.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="2f4586fc40ccf258-b5cdefd1-410d4e1c-8ecc826e-ef9d496845a5d583e5f65871"><ac:parameter ac:name=""> unspecified behavior</ac:parameter></ac:structured-macro>
*unspecified behavior* \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\]
Behavior where the standard provides two or more possibilities and imposes no further requirements on which is chosen in any instance.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="12d66bb513bdb948-fe7cbaa4-41064cc1-a5779582-53710634218eb6553abe89f0"><ac:parameter ac:name=""> validation</ac:parameter></ac:structured-macro>
*validation* \[[IEC 61508-4|AA. C References#IEC 61508-4]\]
Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="0acd96007b66ec24-35fd68d9-4caf4c53-9fcfa65a-74c0182ae0c01446ec3755ab"><ac:parameter ac:name=""> verification</ac:parameter></ac:structured-macro>
*verification* \[[IEC 61508-4|AA. C References#IEC 61508-4]\]
Confirmation by examination and provision of objective evidence that the requirements have been fulfilled.

Wiki Markup
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="769fbfe618b8099a-62f61a65-4b294436-bd80aad2-71be69a2ba9cd9c916cbeadd"><ac:parameter ac:name=""> vulnerability</ac:parameter></ac:structured-macro>
*vulnerability* \[[Seacord 05a|AA. C References#Seacord 05]\]
A vulnerability is a set of conditions that allows an attacker to violate an explicit or implicit security policy.