Jump to content

クロスサイト リクエスト フォージェリ

ショートカット: CSRF
From mediawiki.org
This page is a translated version of the page Cross-site request forgery and the translation is 13% complete.

クロスサイト リクエスト フォージェリ (または CSRF) とは、Web ブラウザーのキャッシュ動作を利用して、Web アプリケーションのセキュリティの脆弱性を突く攻撃の一種です。

CSRF 攻撃は、被害者のブラウザーにキャッシュされた認証情報 (Cookie やキャッシュされたユーザー名とパスワードなど) を利用して、悪意のある HTTP リクエストを認証します。 悪意のある HTTP リクエストは、さまざまな方法で送信できます。 認証情報をキャッシュしている Web ブラウザーでリクエストが処理される限り、CSRF 攻撃を試行できます。 Examples of this include:

  • links included in email messages that are opened in a browser by the victim
  • image tags embedded in HTML-formatted email (which are subsequently viewed in a web email client)
  • forms embedded in a web page
  • AJAX-style requests made via JavaScript

When successful, the attacks can allow the attacker to perform actions on a website with the same level of permissions as the victim.

For a broader overview of cross-site request forgeries, review Wikipedia's Cross-site request forgery page.


The following code snippet helps demonstrate how a CSRF attack could occur. Assume that there are no other checks or protections in place to prevent an attack.

$user = $out->getUser();
$request = $out->getRequest();
if ( $user->isAllowed( 'delete' ) && $request->wasPosted() && $request->getCheck( 'delete' ) ) {
	$this->deleteItem( $request->getText( 'delete' ) );

The code allows a user to delete an item in wiki, as long as they have sufficient permissions and are authenticated.

If an authenticated user is tricked into visiting an external webpage under the control of an attacker, then the attacker can forge a request and send it to the wiki. The wiki would receive the request, check for authentication credentials, and then run the forged request as if it had actually been made by the victim.

Defending MediaWiki against CSRF attacks

We reduce the risk of CSRF attacks in MediaWiki using pseudo-random challenge tokens. These tokens are generated for each page that an authenticated user visits.

When submitting a form for a given page, the submission must include the token. Submissions that do not include the token will fail. It is difficult for attackers to guess or steal these tokens, making CSRF attacks more difficult.

Thanks to JavaScript's same origin policy, attackers cannot easily use JavaScript to read the challenge token from the form.

Implementing Challenge Tokens

Challenge tokens should be added to all forms and all APIs that can make a change (edit, update, delete, block etc.). You might want to look into migrating your code to HTMLForm, which has support for CSRF protection.

HTML Forms

To add the tokens, use the getEditToken() method from the current request 's User instance. The code will look like this:

function showForm( $out ) {
	$user = $out->getUser();
	$out->addHTML( Html::hidden( 'token', $user->getEditToken() ) );

function submitForm() {
	if ( !$user->matchEditToken( $request->getVal( 'token' ) ) ) {
		... CSRF detected - stop the request right now ...
	// OK, continue submit

Every form which performs a write operation should be protected in this way.


If an API performs write operations, it should override isWriteMode to return true and needsToken to return a string indicating the correct token type (usually 'csrf'). Generally, mustBePosted should also return true in this case.

See also