Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-9731: In meta/classes/package_ipk.bbclass in Poky in poky-pyro 17.0.0 for Yocto Project through YP Core - Pyro 2.3,

48
This month
HIGH 7.5REMOTEDOWNGRADE

CVE-2017-9731 is a high-severity flaw (CVSS 7.5) affecting yp core-pyro. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In meta/classes/package_ipk.bbclass in Poky in poky-pyro 17.0.0 for Yocto Project through YP Core - Pyro 2.3, attackers can obtain sensitive information by reading a URL in a Source entry in an ipk package.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.1% (top 34%)
CISA exploited listNo
WeaknessCWE-200
Published2017-06-16
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: yocto project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

yocto project yp core-pyro DOWNGRADE
Affected: 2.3
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.3
1. Check installed version
apt-cache policy yp-core-pyro || rpm -q yp-core-pyro || yp-core-pyro --version
2. No fixed release: DOWNGRADE to a release before 2.3 (Debian / Ubuntu)
apt-cache madison yp-core-pyro sudo apt install yp-core-pyro=<VERSION_BEFORE_2.3> sudo apt-mark hold yp-core-pyro
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list yp-core-pyro sudo dnf downgrade yp-core-pyro-<VERSION_BEFORE_2.3> sudo dnf versionlock add yp-core-pyro
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-9731?

yp core-pyro: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-9731 being exploited?

CVE-2017-9731 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-9731 affect?

CVE-2017-9731 affects yp core-pyro. Severity is high (CVSS 7.5). In meta/classes/package_ipk.bbclass in Poky in poky-pyro 17.0.0 for Yocto Project through YP Core - Pyro 2.3, attackers can obtain sensitive information by reading a URL in a Source entry in an ipk package.

How urgent is CVE-2017-9731?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.