Category:API Abuse - Revision history

Jmanico at 19:22, 5 April 2014

2014-04-05T19:22:22Z

Mchalmers at 19:56, 29 July 2008

2008-07-29T19:56:39Z

Weilin Zhong at 21:16, 4 August 2006

2006-08-04T21:16:16Z

Weilin Zhong at 18:23, 18 July 2006

2006-07-18T18:23:32Z

Weilin Zhong at 18:18, 18 July 2006

2006-07-18T18:18:43Z

Weilin Zhong at 12:38, 18 July 2006

2006-07-18T12:38:55Z

Weilin Zhong at 12:37, 18 July 2006

2006-07-18T12:37:14Z

New page

{{Template:Fortify}}

An API is a contract between a caller and a callee. The most common forms of API abuse are caused by the caller failing to honor its end of this contract. For example, if a program fails to call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller abuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated.

{{Category:Attack}}

← Older revision		Revision as of 19:22, 5 April 2014
Line 1:		Line 1:
−	~~{{Template:Fortify}}~~
−
	==Description==		==Description==

Line 6:		Line 4:

	[[Category:Vulnerability]]		[[Category:Vulnerability]]
−
−	~~{{Stub}}~~

← Older revision		Revision as of 19:56, 29 July 2008
Line 6:		Line 6:

	[[Category:Vulnerability]]		[[Category:Vulnerability]]
		+
		+	{{Stub}}

← Older revision		Revision as of 18:23, 18 July 2006
Line 1:		Line 1:
−	~~#Redirect~~ [[Category:~~API Abuse Attack~~]]	+	{{Template:Fortify}}
		+
		+	An API is a contract between a caller and a callee. The most common forms of API abuse are caused by the caller failing to honor its end of this contract. For example, if a program fails to call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller abuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated.
		+
		+	[[Category:Vulnerability]]

← Older revision		Revision as of 18:18, 18 July 2006
Line 1:		Line 1:
−	~~{{Template:Fortify}}~~	+	#Redirect [[Category:API Abuse Attack]]
−
−	An API is a contract between a caller and a callee. The most common forms of API abuse are caused by the caller failing to honor its end of this contract. For example, if a program fails to call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller abuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated.
−
−	[[Category:Attack]]

← Older revision		Revision as of 12:38, 18 July 2006
Line 3:		Line 3:
	An API is a contract between a caller and a callee. The most common forms of API abuse are caused by the caller failing to honor its end of this contract. For example, if a program fails to call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller abuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated.		An API is a contract between a caller and a callee. The most common forms of API abuse are caused by the caller failing to honor its end of this contract. For example, if a program fails to call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller abuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated.

−	{{Category:Attack}}	+	[[Category:Attack]]

@@ Line 1: / Line 1: @@
 {{Template:Fortify}}
 An API is a contract between a caller and a callee. The most common forms of API abuse are caused by the caller failing to honor its end of this contract. For example, if a program fails to call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller abuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated.
 [[Category:Vulnerability]]