Last modified: 2007-01-30 19:44:33 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T10829, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8829 - False positive on Spam Blacklist filter
False positive on Spam Blacklist filter
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-30 15:47 UTC by Mike Dillon
Modified: 2007-01-30 19:44 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Mike Dillon 2007-01-30 15:47:25 UTC
On English Wikipedia and Meta, the following text is triggering the spam blacklist:

    <div style="overflow:auto; height: 10em;"/>

The error message is "The following text is what triggered our spam filter:
overflow:auto; height:". I was able to work around it by reversing the
"overflow" and "height" properties.

I tried to track it down in the code, but I couldn't find the culprit. It may be
related to the setting of $wgUrlProtocols on the Wikimedia servers, but I don't
know that that setting is. The setting in DefaultSettings.php wouldn't have this
problem. I don't have access to a local MediaWiki install at the moment to test.
Comment 1 Rob Church 2007-01-30 16:22:52 UTC
I expect we're filtering out 'style="overflow: auto"' since it's often used in
mass spam and vandalism attacks; this would be set in $wgSpamRegex.
Comment 2 Brion Vibber 2007-01-30 16:36:15 UTC
Correct, that is indeed in the filter.
Comment 3 Daniel Kinzler 2007-01-30 16:41:18 UTC
i expect spammers will soon start to revert those attributes too, or inject
random cruft to obfuscate them. the spam-regex would need to be more flexible to
catch that. and would then prevent any such workarounds from working any longer.
Comment 4 Mike Dillon 2007-01-30 19:44:33 UTC
This is disappointing.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links