Studio Onsite vulnerabilitiesAnd the versions its exploited flaws hit.
Studio Onsite is made by Suse. We track 22 published vulnerabilities listed under that exact name, across 8 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 28 January 2022. Suse lists newer releases under their own names, such as Studio Onsite Appliance, so check those pages too.
The most recent Studio Onsite flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022. We keep watching the known-exploited list.
Is Studio Onsite listed under other names? Yes.
Suse also lists Studio Onsite under more specific names, such as Studio Onsite Appliance. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which versions of Studio Onsite do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2014-6271Exploited list, 28 Jan 2022
GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
1.3 - CVE-2014-7169Exploited list, 28 Jan 2022
GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
1.3
Which Studio Onsite vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.
- 9.8GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.
Which Studio Onsite flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment, as demonstrated by...
- >99%
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or possibly have unknown...
- 68%CVE-2013-4547High
nginx 0.8.41 through 1.4.3 and 1.5.x before 1.5.7 allows remote attackers to bypass intended restrictions via an unescaped space character in a URI.
- 50%CVE-2016-5118Critical
The OpenBlob function in blob.c in GraphicsMagick before 1.3.24 and ImageMagick allows remote attackers to execute arbitrary code via a | (pipe) character at the start of a filename.
- 18%CVE-2015-1283Medium
Multiple integer overflows in the XML_GetBuffer function in Expat through 2.1.0, as used in Google Chrome before 44.0.2403.89 and other products, allow remote attackers to cause a denial of service (heap-based buffer...
- 13%CVE-2016-0718Critical
Expat allows context-dependent attackers to cause a denial of service (crash) or possibly execute arbitrary code via a malformed input document, which triggers a buffer overflow.
- 6.0%CVE-2011-4315Medium
Heap-based buffer overflow in compression-pointer processing in core/ngx_resolver.c in nginx before 1.0.10 allows remote resolvers to cause a denial of service (daemon crash) or possibly have unspecified other impact...
- 4.9%CVE-2014-9846Critical
Buffer overflow in the ReadRLEImage function in coders/rle.c in ImageMagick 6.8.9.9 allows remote attackers to have unspecified impact.
- 2.6%CVE-2011-3180High
kiwi before 4.98.08, as used in SUSE Studio Onsite 1.2 before 1.2.1 and SUSE Studio Extension for System z 1.2 before 1.2.1, allows attackers to execute arbitrary commands via shell metacharacters in the path of an...
- 2.1%CVE-2014-9844Medium
The ReadRLEImage function in coders/rle.c in ImageMagick 6.8.9.9 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted image file.
Running Studio Onsite? 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 flaw being exploited affects software Acme tracks
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.
- Matched to
- Studio Onsite on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 22 published vulnerabilities listed under the name Studio Onsite, across 8 versions. The most recent Studio Onsite flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2014-6271 and CVE-2014-7169.
Suse also lists Studio Onsite under more specific names, such as Studio Onsite Appliance. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2014-6271, affects 1.3. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Studio Onsite. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.