Talk:Exploit (computer security)

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
WikiProject Computer Security / Computing  (Rated Start-class, High-importance)
WikiProject iconThis article is within the scope of WikiProject Computer Security, a collaborative effort to improve the coverage of computer security on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start This article has been rated as Start-Class on the project's quality scale.
 High  This article has been rated as High-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing.
 
Things you can help WikiProject Computer Security with:
Newspaper.svg
Article alerts will be generated shortly by AAlertBot. Please allow some days for processing. More information...
  • Answer question about Same-origin_policy
  • Review importance and quality of existing articles
  • Identify categories related to Computer Security
  • Tag related articles
  • Identify articles for creation (see also: Article requests)
  • Identify articles for improvement
  • Create the Project Navigation Box including lists of adopted articles, requested articles, reviewed articles, etc.
  • Find editors who have shown interest in this subject and ask them to take a look here.
WikiProject Computing (Rated Start-class)
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start This article has been rated as Start-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
 

An exploit may or may not 'extend privileges'. It could cicumvent access control, or entend it to provide or extends access to a feature _or_ allows a feature to be used in a manner not intended by the softwares developers.

there are always such misfeatures, bugs, holes, whatever you wanna call 'em. It's best not to distinguish but imagine software itself as swiss cheese that one grabs onto by fumbling fingers in the dark, some of which give access to the center and let you grab the whole cheese, take it out of the dark, adn eat it.

This is supposed to be an encyclopedia, its whole premises is centered on completeness and accuracy.

This is not computer science[edit]

The term "exploit" as defined here is not a computer science term. It is a term from computer security operations. I propose that this article be moved to Exploit (computer security). Any objections? --FOo 14:29, 18 Aug 2004 (UTC)

Well, nobody objected in a few months, so moved it is. --FOo 04:24, 4 Feb 2005 (UTC)

Numerious problems[edit]

I really feel that this article could be brought up to the level of wikipedia's other computer related articles, but as I am not a hacker or person skilled in computer security, I do not feel comfortable attempting to do this myself. A number of problems that concerned me about this article follow. I have restrained myself to improving the initial definition to be a bit more broad and complete.

The first problem is the distinction between a remote and local exploit. While these are terms that should be discussed, as they are in common usage, not all exploits will fall into one of these two catagories and is therefore not a universal classification.

I feel that a more general description of an exploit should include that an exploit is something that "exploits" a programming bug, setup bug, or abuses a feature. Does anyone have any comments on this? Immediately talking about common types of exploits misses that these are all types of bugs, and that exploit finding is really a subset of bug finding.

It's pedantic of me to point this out, but the term super-user is unix/linux/bsd/*nix specific. Going back to my broader definition, I would like to use a hypothetical example. Many (all?) elevators in the United States have telephones in them for communication with the elevator's users durring an emergency. An unintended or incidental behavor exists however, in that in some elevators it is possible, given the correct phone number, to call the phone inside the elevator and listen to people inside. I would consider this an unintended use of an elevator feature, and therefore an exploit. This does not include getting extra access to a computer, any of the vulnerablity types mentioned, and appears to be outside the current stated scope of the article. Would this be considered an exploit?

I really think that this article could be brought up to the level of one of wikipedia's computer science articles, include broad examples, and include a holistic aproach to viewing exploits as a subset of bug finding.

Lastly, return to libc is not an attack, it is a technique used when control of a return address on the stack has been obtained. Please correct me if I am wrong about this.

-- Unfortunetly not anonymous user, November 7, 2006

Comments on numerous problems[edit]

The typical problem with any computer/information security discussion on wikipedia is nobody agrees on (and fewer people have a correct understanding of the nomenclature). This article confuses exploits, vulnerabilities and threats. I'd suggest dropping all the unsourced statements and start again. —Preceding unsigned comment added by 142.46.212.114 (talk) 19:55, 23 October 2007 (UTC)Reply[reply]

Requested move 25 March 2018[edit]

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: consensus not to move the pages at this time, per the discussion below. Dekimasuよ! 18:33, 31 March 2018 (UTC)Reply[reply]


– This article makes sense as the WP:PRIMARYTOPIC. It gets 290 views daily with the video game article only getting 33 views daily, and while Exploitation of natural resources gets a lot of views, nobody would type in "Exploit" to look up that article, they would more likely type Exploitation. As the clear winner in terms of pageviews and precedence for the term "Exploit", it should be primary. ZXCVBNM (TALK) 12:54, 25 March 2018 (UTC)Reply[reply]

  • Oppose Per WP:PTOPIC: "no single criterion for defining a primary topic, two major aspects that are commonly considered are [usage] and [long-term significance]"..."consensus may be useful in determining which topic, if any, is the primary topic." My input is it remain how it is, the term "exploit" has been used to describe labor and resources far longer than video games and computers. Also note PTOPIC's mention of Apple vs Apple Inc. Internet clicks is irrelevant, it doesn't give the whole picture. Having the disambiguation as the primary is a fair compromise already. DA1 (talk) 17:09, 25 March 2018 (UTC)Reply[reply]
    • You are talking about the word "exploitation". "Exploit" on its own is not used to describe labor and resources, hence why it's called "labor exploitation" and not "labor exploits". There is a difference, which is why this should point to the subject that uses "Exploit". A hatnote can clear up any confusion.ZXCVBNM (TALK) 20:25, 25 March 2018 (UTC)Reply[reply]
  • Oppose exploit is a common noun, and verb. This obscure computer security use would be WP:ASTONISHing. So far from a WP:PT surprised to see an RM In ictu oculi (talk) 08:36, 26 March 2018 (UTC)Reply[reply]
  • Oppose – does not make sense as primarytopic. Dicklyon (talk) 02:52, 27 March 2018 (UTC)Reply[reply]
  • Oppose. Oh please! Clearly no primary topic for this common English word. -- Necrothesp (talk) 13:31, 28 March 2018 (UTC)Reply[reply]

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.