Sign inStart freeBook a demo

What is CVE-2016-0708?A medium-severity flaw in Java Buildpack, explained.

Medium severity2 affected products
The short answer

CVE-2016-0708 is a medium-severity flaw (CVSS 5.9) in Java Buildpack from Cloudfoundry, published on 11 July 2018. 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 1.6%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 11 July 2018. Record last updated 11 September 2018. We keep this page's data up to date.

What it does

What is CVE-2016-0708? In plain terms.

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data.

The official description

Applications deployed to Cloud Foundry, versions v166 through v227, may be vulnerable to a remote disclosure of information, including, but not limited to environment variables and bound service details. For applications to be vulnerable, they must have been staged using automatic buildpack detection, passed through the Java Buildpack detection script, and allow the serving of static content from within the deployed artifact. The default Apache Tomcat configuration in the affected java buildpack versions for some basic web application archive (WAR) packaged applications are vulnerable to this issue.

What kind of flaw is it?

  • CWE-200Exposure of Sensitive Information to an Unauthorized Actor
CVSS 3.0 scoreMedium · 5.9

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 offHard: conditions must line up
  • Login needed firstNo login needed
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan read data

Severity vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation

Is CVE-2016-0708 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 1.6%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days1.6%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
24out of 100Low

CVE-2016-0708 scores 24. 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-2016-0708 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2016-0708? 2 products.

The published record lists 2 products from 1 vendor. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2016-0708? Four steps.

  1. 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.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. 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.
  4. 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

1 link
Precursor Intelligence

Does CVE-2016-0708 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2016-0708 is a medium-severity flaw in Java Buildpack from Cloudfoundry, published on 11 July 2018. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data.

It scores 5.9 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2016-0708 is 24 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 1.6%. That can change at any time, which is why we keep watching.

For Java Buildpack from Cloudfoundry: 2.0 to 3.4. 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.

Keep exploring