CVE reports is publicly identified types of vulnerability found in systems and internet. These vulnerability found in system are categorized in different different topics, these topics have lots of method to found in one of many systems, software and web applications. This method is what can be identified uniquely.
CVE reports are publicly available and can be found by CVE code like "CVE IDs," "CVE entries," "CVE names," "CVE numbers," and "CVEs" which is from four or more numbers. These numbers are unique and commonly identified anywhere in the internet. As cyber security vulnerabilities, it is identified like "CVE-1999-0067", "CVE-2000-1205", "CVE-2016-1234".
CVE is used from 1999 on that time there is no easy way identification to find out if the vulnerability are same or not based on the different status of reports found in local servers or in personal used database. This result in many problems like differences between id numbers found in different database.
Exploit a term of direct use of resource! A thread of program to have direct benefit of resource. In offense of security of a program or software which have a dynamic or uncontrollable flaw can be exploit, which give a term of resource access by unidentified program.
Exploit is a piece of code which can not be detected by security program, It behave with program like there own code. These code or program have there flaw to work. Exploit is just use that flaw to fit and access what is its program for. Right now there is widely used programming languages for both web or non web programs like C, Dot Net(.Net), php, asp, java, html, xml etc.
Is programming language is secure from exploit?
Exploit is not ask for programming language, It just depend on programmer. Program which use dynamic flaw can be exploited, there is no exception in programming language. Because today most program are used for dynamic concept where program take input on run time or want changes in there program as without following all process from the start.
Note :
If you are a beginner and you don't know the dynamic concept than you may not understand about exploit and security.
What exploit can do?
Exploit is just a word or command which is not need to ask for permission. So exploit term itself is offensive to use. For security reason you should have known the program and its language to check if your program can be exploit or not.
Greetings
readers, I found a one of critical bug on investor[dot]fb[dot]com,
However the risk severity is medium and hard to exploit remotely but
still it is a security bug. Yes!! I'm talking about user-agent header
cross site scripting vulnerability on one of subdomain of fb.com. As a
information security researcher and whitehat mindset, I reported it to
Facebook so that they can fix this issue but in response I found this is
not a issue for them and finally I asked to him to make a writeup on
this bug and all seems they don't care about it.
Whatever,
let me explain this bug. As all of you know, browser always sent
user-agent with HTTP request and user can change user-agent by
intercepting the request or via some plugins but I'm fan of "Tamper
Data" - a Firefox plugin that allow user to intercept request easily.
When I was trying to find some bugs on investor.fb.com, I found a link investor.fb.com/alerts.cfm
that contains a form with some checkboxes and can use POST method.
First of all I tick on checkbox and submit the data by clicking continue
button, at same time I intercepted the request and make some changes in
value of checkbox i.e. doublequote and get this error message -
If
you look at this error message, you will notice it contains the
User-Agent. So suddenly a thing stuck on my mind and I modified
user-agent to XSS Payload. After that XSS Payload i.e. User-Agent:<img src=x onerror=prompt(document.domain);> will take place of user-agent and popup a javascript prompt.
Now
let's discuss about risk severity and vulnerability of XSS in
user-agent. This kind of bug is not easy to exploit remotely though some
advanced method allow to exploit this vulnerability otherwise this will
be self-xss. In normal cases, only client can execute this kind of bug
on their system but I think nobody, even a newbie will not going to
change user-agent for you. Then I found a very informative article on
internet that shows the fabulous way of triggering user-agent XSS. -
http://websecurity.com.ua/5195/
Status: Reported [Unpatched] Disclaimer: This article is only for education and knowledge purpose only.
