What is CVE-2011-0990?A medium-severity flaw in Mono, explained.
CVE-2011-0990 is a medium-severity flaw (CVSS 5.8) in Mono, published on 13 April 2011. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 2.2%. If you run an affected version, plan in the vendor’s fix.
Published 13 April 2011. Record last updated 16 June 2026. We keep this page's data up to date.
What is CVE-2011-0990? In plain terms.
It can be attacked from anywhere on the internet without logging in. If it works, the attacker can change some data and slow it down.
Race condition in the FastCopy optimization in the Array.Copy method in metadata/icall.c in Mono, when Moonlight 2.x before 2.4.1 or 3.x before 3.99.3 is used, allows remote attackers to trigger a buffer overflow and modify internal data structures, and cause a denial of service (plugin crash) or corrupt the internal state of the security manager, via a crafted media file in which a thread makes a change after a type check but before a copy action.
What kind of flaw is it?
- CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offSome conditions needed
- Login needed firstNo login needed
- What an attacker getsCan change some data and slow it down
Severity vector: AV:N/AC:M/Au:N/C:N/I:P/A:P
Is CVE-2011-0990 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.2%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2011-0990 scores 20. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2011-0990 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2011-0990? 2 products.
The published record lists 2 products from 2 vendors. If you run one of these, check your version, then go to the fix below.
How do I fix CVE-2011-0990? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
10 linksDoes CVE-2011-0990 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Race condition in the FastCopy optimization in the Array.Copy method in metadata/icall.c in Mono, when Moonlight 2.x before 2.4.1 or 3.x before 3.99.3 is use...
- Matched to
- Mono on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2011-0990 is a medium-severity flaw in Mono, published on 13 April 2011. It can be attacked from anywhere on the internet without logging in. If it works, the attacker can change some data and slow it down.
It scores 5.8 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2011-0990 is 20 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.2%. That can change at any time, which is why we keep watching.
For Mono: all versions. The record lists 2 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.