See the installation instructions for details, but it's easy:

• macOS: brew install ddev/ddev/ddev or just brew upgrade ddev.
• Linux: Use sudo apt-get update && sudo apt-get install ddev, see apt/yum installation
• Windows and WSL2: Download the Windows Installer; you can run it for install or upgrade.
  ⚠️ Traditional Windows users (not WSL2): If needed, the installer will prompt you to uninstall the previous system-wide installation to avoid conflicts with the new per-user installation.
• Consider ddev delete images or ddev delete images --all after upgrading to free up disk space used by previous Docker image versions. This does no harm.
• Consider ddev config --auto to update your projects to current configuration.

Highlights

• Faster ddev start: Reduced fresh-router healthcheck wait
• New project types and quickstarts: 3 new project types (wp-bedrock, asterios, joomla) and 2 new quickstarts (Tempest, October CMS)
• Auto-start on command: DDEV now automatically starts stopped projects when you run ddev exec, ddev ssh, ddev share, ddev xhgui, ddev pull, ddev push, or ddev snapshot restore
• New diagnostic commands: ddev utility port-diagnose to identify port conflicts, ddev utility check-custom-config to detect unexpected configuration, ddev utility tls-diagnose to identify TLS/SSL problems with DDEV projects.

Quickstarts

• Add wp-bedrock project type, thanks to @jonesrussell
• Add asterios project type, thanks to @asteriosphp
• Add joomla project type, thanks to @renekreijveld
• Add Tempest quickstart
• Add October CMS quickstart, thanks to @daftspunk
• Update Contao quickstart to use 5.7 LTS, thanks to @fkaminski
• Update Laravel quickstart to latest version, thanks to @tyler36
• Update Moodle quickstart to set admin email during installation

Features

• Support bare variable names in web_environment for host environment passthrough
• Add project path to the interactive dashboard, thanks to @yanniboi
• Add global omit_snapshot_on_delete setting, thanks to @marklabrecque-ab
• Add --project flag to ddev exec, thanks to @penyaskito
• Use runtime environment variables in wp-config-ddev.php for WordPress, thanks to @jonesrussell
• Add support for symfony_mailer 2.x in Drupal config, thanks to @hchonov
• Display project info (name and environment) when calling ddev pull/ddev push, thanks to @mariano-dagostino
• Support virtioproxy WSL2 networking mode
• Support "1"/"0" for DDEV_* environment variables (e.g. DDEV_DEBUG=1), thanks to @deviantintegral
• Automatically set com.ddev.* labels for Docker images, containers, and networks
• Add aggregate_gc_threshold=0 to Drupal 12 config, thanks to @rpkoller

Bug Fixes

• Detect custom configuration files and show unexpected configuration on ddev start
• Prevent Path Traversal (ZipSlip), thanks to @SnailSploit
• Normalize PHP_IDE_CONFIG (PhpStorm) for uppercase project names
• Reduce file permissions for system directories /usr/bin and /usr/sbin inside the container, thanks to @AkibaAT
• Ensure ddev-ssh-agent and ddev-router are up to date on DDEV upgrade
• Respect webimage for all use cases; don't pull the default web image when it's not in use
• Simplify ddev composer create-project by removing the composer update step
• Add timeout to yarn config set in start.sh for the ddev-webserver Docker image
• Fix malformed WSLENV on Windows install/uninstall

Internal Improvements

• Implement config model using Viper, thanks to @agviu
• Improve testing in GoLand by prebuilding the ddev binary, thanks to @jonesrussell
• Add missing php8.5-memcached for ARM64 to ddev-webserver Docker image
• Use newer deb822 format (*.sources instead of *.list) for Docker and DDEV repositories (Linux and WSL2)

Minor Updates

• PHP 8.4.20 and 8.5.5
• Docker Compose v5.1.3
• Remove obsolete ddev sequelpro command and vestiges in documentation

What's Changed

• fix(commands): use /usr/bin/env bash in web console command by @tyler36 in #8182
• build(deps): bump actions/upload-artifact from 6 to 7 by @dependabot[bot] in #8193
• fix(composer): ddev composer create-project can ignore .devcontainer [skip buildkite] by @rfay in #8192
• docs(buildkite): Minor fixups to WSL2 buildkite setup by @rfay in #8172
• build(deps): bump goreleaser/goreleaser-action from 6 to 7 by @dependabot[bot] in #8175
• docs(quickstart): Use mkdir -p and more descriptive names [skip buildkite] by @rfay in #8200
• docs: suggest trivial project in troubleshooting by @rfay in #8199
• build(deps): bump docker/login-action from 3 to 4 (#8211) [skip ci] by @dependabot[bot] in #8211
• build(deps): bump docker/setup-buildx-action from 3 to 4 by @dependabot[bot] in #8210
• docs: clarify usage for TUI by @stasadev in #8203
• test(quickstart): pause d12 bats test in github actions by @rpkoller in #8217
• chore(docs): remove Plausible [skip ci] by @stasadev in #8228
• fix(quickstart): do not use gunicorn for wagtail by @stasadev in #8229
• feat: support bare variable names in web_environment for host env passthrough by @rfay in #8209
• fix(buildkite): use proper check for skip by @stasadev in #8231
• build: update go deps, vendor docker-compose SDK, for #8234 by @stasadev in #8198
• style: Fix minor typo: skiped → skipped by @penyaskito in #8243
• chore(quickstart): Make quickstart drupal.bats drush launch usage less fragile by @rfay in #8247
• fix: prevent path traversal (ZipSlip) in Untar and Unzip by @rfay in #8213
• fix: lowercase PHP_IDE_CONFIG serverName for uppercase project names, fixes #8225 (#8248) [skip ci] by @rfay in #8248
• docs(sharing): Improve ngrok setup instructions, fixes #8101 (#8205) [skip ci] by @samcrichard in #8205
• refactor: bump Laravel to latest version by @tyler36 in #8238
• chore(go): Use go fix to update golang usage, fixes #7963 by @rfay in #8249
• feat(tui): Added ddev project path to TUI project browser, for #8184 by @yanniboi in #8185
• build: update go deps, vendor viper, for #8181 by @dependabot[bot] in #8237
• fix: reduce world writeable directories and files, fixes #8194 by @AkibaAT in #8195
• feat: add aggregate_gc_threshold of 0 to drupal12 settings.ddev.php (#8215) [skip ci] by @rpkoller in #8215
• build(pecl): add php8.5-memcached for ARM64, fixes ddev/ddev-memcached#20 by @stasadev in #8252
• docs: document Mailpit plus-address auto-tagging and how to disable it (#8222) [skip ci] by @maks-oleksyuk in #8222
• fix: use Lstat in PurgeDirectory to handle symlinks without following them by @rfay in #8254
• build: bump 1password/load-secrets-action from 3 to 4 (#8266) [skip ci] by @dependabot[bot] in #8266
• fix(test): check for GitHub token in TestAddonGetCircularDependencies by @stasadev in #8257
• fix(docker): use ContainerInspect polling instead of ContainerWait to avoid hangs by @stasadev in #8265
• fix: bump action-linkspector from v1.3.5 to v1.4.0 to resolve setup-node@v4 warning [skip ci] by @rfay in #8269
• fix: use deb822 format for DDEV and Docker apt repositories, fixes #8232 (#8233) [skip ci] by @stasadev in #8233
• feat(autostart): automatically start projects on command when project stopped, fixes #8245 by @rfay in #8258
• test(lagoon): use new amazee.io testing environment for Lagoon integration (#8270) [skip ci] by @rocketeerbkw in #8270
• build(arm64): php8.5-memcached from repos, refactor ddev-webserver tests, for #8252 by @stasadev in #8268
• test(webserver): wait for FPM reload to settle after xdebug disable (#8272) [skip ci] by @stasadev in #8272
• refactor: implement config model using viper, fixes #5763 (#8181) [skip ci] by @agviu in #8181
• feat(cmd): ddev exec accepts a --project flag, fixes #8241 by @penyaskito in #8244
• feat(wordpress): use runtime DDEV_PRIMARY_URL for WP_HOME, fixes #8098 by @jonesrussell in #8176
• chore(drupal): add support for symfony_mailer 2.x to drupal settings.ddev.php by @hchonov in #8274
• test(wsl2): add cleanup for ddev/docker apt sources leftovers, for #8233 by @stasadev in #8275
• feat: Display project info (name and environment) when calling ddev pull/push, fixes #8201 by @mariano-dagostino in #8202
• fix(config): detect custom files, add ddev utility check-custom-config by @stasadev in #8218
• fix(docker): use ddev-utilities image for volume/utility RunSimpleContainer calls to fix Lima/Colima 10-30m hangs by @rfay in #8271
• test(traefik): skip TestCustomGlobalConfig on Rancher Desktop, fixes #8167 (#8283) [skip ci] by @rfay in #8283
• fix(docker): use ddev-utilities for remaining RunSimpleContainer calls (#8282) [skip ci] by @rfay in #8282
• fix(mutagen): tolerate transient staging files during volume chown by @rfay in #8281
• refactor: detect custom files in ddev utility diagnose by @stasadev in #8279
• docs: Update Contao Quickstart Recipe (#8278) [skip ci] by @fkaminski in #8278
• docs: improve AI agent instructions and dev workflow guidance [skip ci] (#8284) [skip ci] by @rfay in #8284
• fix(addons): sleep 500ms after creating config files on Lima/Colima/Rancher Desktop (#8288) [skip ci] by @rfay in #8288
• chore: remove obsolete commands, fixes #8291 (#8292) [skip ci] by @stasadev in #8292
• fix: normalize path separators in check-custom-config output on Windows by @rfay in #8286
• docs: add october cms to quickstart instructions (#8285) [skip ci] by @daftspunk in #8285
• test: fail fast when command tests would use PATH ddev by @jonesrussell in #8280
• build(ci): pin textlint@15.5.2 by @stasadev in #8300
• refactor(wordpress): make wp-config-ddev.php a static asset, fixes #8098 by @rfay in #8287
• docs: rewrite Windows installation instructions, fixes #7996, fixes #7703 (#8290) [skip ci] by @rfay in #8290
• docs(quickstart): add Tempest (#8299) [skip ci] by @stasadev in #8299
• feat: support "virtioproxy" WSL2 networking mode, fixes #8220 by @rfay in #8262
• build(ci): remove pin for textlint, for #8300 (#8303) [skip ci] by @stasadev in #8303
• fix: ensure up-to-date images for ddev-ssh-agent and ddev-router (#8305) [skip ci] by @stasadev in #8305
• fix(webserver): always use webimage from app config (#8304) [skip ci] by @stasadev in #8304
• feat: add global omit_snapshot_on_delete setting, fixes #8263 (#8264) [skiop ci] by @marklabrecque-ab in #8264
• feat: support "1" for environment variables by @deviantintegral in #8246
• chore: add link to blog about buildx requirement, for #8234 (#8310) [skip ci] by @stasadev in #8310
• build: bump actions/github-script from 8 to 9 by @dependabot[bot] in #8314
• fix(composer): remove composer update from create-project, for #7864 (#8315) [skip ci] by @stasadev in #8315
• fix(webserver): add timeout to yarn config set in start.sh (#8309) [skip ci] by @stasadev in #8309
• refactor(debug): simplify RunSimpleContainer reporting, for #8271 (#8311) [skip ci] by @stasadev in #8311
• feat: add ddev utility port-diagnose command to identify port conflicts, fixes #8085 (#8260) [skip ci] by @rfay in #8260
• feat: add wp-bedrock project type, fixes #8179 by @jonesrussell in #8219
• feat(docker): set ddev labels for images, containers, networks, fixes #7389 by @stasadev in #8312
• refactor(debug): improve reporting for RunSimpleContainer timeout, for #8311 by @stasadev in #8317
• perf(router): reduce fresh-router healthcheck wait, refs #8096 by @rfay in #8316
• test: update moodle quickstart by @stasadev in #8319
• fix(test): use local apt repo with fake packages to avoid flakiness in TestExtraPackages by @stasadev in #8323
• feat(asterios): Add Asterios project type (#8313) [skip ci] by @asteriosphp in #8313
• feat: add ddev utility tls-diagnose command, fixes #8224 (#8259) [skip ci] by @rfay in #8259
• fix(installer): fix malformed WSLENV on Windows install/uninstall, fixes #8324 (#8325) [skip ci] by @rfay in #8325
• fix(traefik): don't mark README.txt as stale (#8329) [skip ci] by @stasadev in #8329
• build(deps): bump go.mod and docker-compose to v5.1.3 by @stasadev in #8318
• test(wsl): mkcert installation on Windows too hard for WSL by @rfay in #8333
• refactor: remove obsolete ddev sequelpro command (#8331) [skip ci] by @rfay in #8331
• feat: add joomla project type by @renekreijveld in #8226
• build(docker): bump images to v1.25.2 for release, fixes #8320 by @stasadev in #8332
• build(ci): remove -failfast, support MAKE_TARGET/TESTPKG/TESTFILE for targeted test runs, increase timeout to 6h by @rfay in #8336
• ci: improve Buildkite test result visibility for FAIL/PASS/SKIP (#8338) [skip ci] by @rfay in #8338
• test(wsl): fix CAROOT propagation for buildkite-agent on WSL2 by @rfay in #8334
• chore(assets): add .ddev/addon-metadata/README.txt (#8343) [skip ci] by @stasadev in #8343
• fix: flush Mutagen before container chmod and after settings file write, fixes #8340 (#8341) [skip ci] by @rfay in #8341
• fix: warn instead of silently ignoring RemoveProjectInfo error, for #8339 (#8342) [skip ci] by @rfay in #8342
• fix(installer): prevent CI timeout in WSL2 Docker CE installer test by @rfay in #8337

New Contributors

• @samcrichard made their first contribution in #8205
• @hchonov made their first contribution in #8274
• @mariano-dagostino made their first contribution in #8202
• @daftspunk made their first contribution in #8285
• @marklabrecque-ab made their first contribution in #8264
• @asteriosphp made their first contribution in #8313
• @renekreijveld made their first contribution in #8226

Full Changelog: v1.25.1...v1.25.2

Intels vorläufig aktuellster GPU-Treiber „8331“ war bereits am 3. Dezember des letzten Jahres erschienen und hatte damit bereits einige Wochen auf dem Buckel, doch jetzt gibt es einen Nachfolger. Der „32.0.101.8425“ ist die neueste Iteration für Arc-Grafikkarten, der laut Release Notes für zwei neue Spiele optimiert ist.

This blog post presents internal photos of the DMX958XR boards and highlights each of the interesting components. A hidden debugging interface is also detailed which can be leveraged to obtain a root shell.

Internals

The DMX958XR is a compact unit that contains multiple interconnected boards. Fortunately, the most interesting board is at the top of the unit and can be easily accessed by removing a few screws and metal plates.

The topside of the main board contains a video processing IC, PMIC, NAND flash, and two DDR3 SDRAMs.

Carefully flipping the main board over reveals the SoC, radio module, eMMC, and more RAM. Be careful not to tear the ribbon cable that is attached to the underside of the board!

In the center of Figure 2 is a Murata radio module that handles Wi-Fi and Bluetooth operations. Searching around for the exact model number that is etched onto the shielding does not return much information, but the FCC documents for the DMX958XR state that this is the Murata LBEE6ZZ1WD-334. This module has no public datasheet available and isn't listed on Murata's site.

To the right of the radio module is the Telechips TCC8974 SoC, which is marketed as an "IVI and Cluster solution" that supports running Android, Linux, and QNX. The TCC8974 uses a 32-bit ARM core and has multimedia hardware acceleration capabilities. Off to the right of the SoC is the supporting SDRAM and eMMC that the TCC8974 requires.

For completeness, annotated photos of the other boards are provided below. These boards serve varying purposes, such as GPS and audio.

Debug Connector

Eagle-eyed readers may have noticed a suspicious-looking edge connector shown in Figure 1 that is slightly off to the right of the NAND flash. This exposes a Linux login prompt over UART at 115200bps. Logging in with the correct credentials will spawn a root shell.

Summary

Hopefully, this blog post provides enough information to kickstart vulnerability research against the DMX958XR. Keep an eye out for future posts that cover the threat landscape of the DMX958XR.

We are looking forward to Automotive Pwn2Own, again to be held in January 2025 at the Automotive World conference in Tokyo. We will see if IVI vendors have improved their product security. Do not wait until the last minute to ask questions or register! We hope to see you there.

You can find me on Twitter at @ByteInsight, and follow the team on Twitter, Mastodon, LinkedIn, or Bluesky for the latest in exploit techniques and security patches.

19th July, 2017

tiff vulnerabilities

A security issue affects these releases of Ubuntu and its derivatives:

• Ubuntu 12.04 LTS

Summary

LibTIFF could be made to crash or run programs as your login if it opened a specially crafted file.

Software description

• tiff - Tag Image File Format (TIFF) library

Details

USN-3212-1 and USN-3212-2 fixed a vulnerabilitiy in LibTIFF. This update provides a subset of
corresponding update for Ubuntu 12.04 ESM.

Original advisory details:

It was discovered that LibTIFF incorrectly handled certain malformed
images. If a user or automated system were tricked into opening a specially
crafted image, a remote attacker could crash the application, leading to a
denial of service, or possibly execute arbitrary code with user privileges.

Update instructions

The problem can be corrected by updating your system to the following package version:

Ubuntu 12.04 LTS:

libtiff4 3.9.5-2ubuntu1.10

libtiff-tools 3.9.5-2ubuntu1.10

To update your system, please follow these instructions: https://wiki.ubuntu.com/Security/Upgrades.

In general, a standard system update will make all the necessary changes.

References

CVE-2015-7554, CVE-2015-8668, CVE-2016-10092, CVE-2016-3623, CVE-2016-3624, CVE-2016-3632, CVE-2016-3990, CVE-2016-3991, CVE-2016-5321, CVE-2016-5322, CVE-2016-8331, CVE-2016-9453, CVE-2016-9533, CVE-2016-9534, CVE-2016-9536, CVE-2016-9537

27th February, 2017

tiff vulnerabilities

A security issue affects these releases of Ubuntu and its derivatives:

• Ubuntu 16.10
• Ubuntu 16.04 LTS
• Ubuntu 14.04 LTS

Summary

LibTIFF could be made to crash or run programs as your login if it opened a specially crafted file.

Software description

• tiff - Tag Image File Format (TIFF) library

Details

It was discovered that LibTIFF incorrectly handled certain malformed
images. If a user or automated system were tricked into opening a specially
crafted image, a remote attacker could crash the application, leading to a
denial of service, or possibly execute arbitrary code with user privileges.

Update instructions

The problem can be corrected by updating your system to the following package version:

Ubuntu 16.10:

libtiff5 4.0.6-2ubuntu0.1

libtiff-tools 4.0.6-2ubuntu0.1

Ubuntu 16.04 LTS:

libtiff5 4.0.6-1ubuntu0.1

libtiff-tools 4.0.6-1ubuntu0.1

Ubuntu 14.04 LTS:

libtiff5 4.0.3-7ubuntu0.6

libtiff-tools 4.0.3-7ubuntu0.6

To update your system, please follow these instructions: https://wiki.ubuntu.com/Security/Upgrades.

In general, a standard system update will make all the necessary changes.

References

CVE-2015-7554, CVE-2015-8668, CVE-2016-10092, CVE-2016-10093, CVE-2016-10094, CVE-2016-3622, CVE-2016-3623, CVE-2016-3624, CVE-2016-3632, CVE-2016-3658, CVE-2016-3945, CVE-2016-3990, CVE-2016-3991, CVE-2016-5314, CVE-2016-5315, CVE-2016-5316, CVE-2016-5317, CVE-2016-5320, CVE-2016-5321, CVE-2016-5322, CVE-2016-5323, CVE-2016-5652, CVE-2016-5875, CVE-2016-6223, CVE-2016-8331, CVE-2016-9273, CVE-2016-9297, CVE-2016-9448, CVE-2016-9453, CVE-2016-9532, CVE-2016-9533, CVE-2016-9534, CVE-2016-9535, CVE-2016-9536, CVE-2016-9537, CVE-2016-9538, CVE-2016-9539, CVE-2016-9540, CVE-2017-5225

Die Schwachstelle wurde am 28.10.2016 publik gemacht. Die Verwundbarkeit wird unter CVE-2016-8331 geführt. Der Angriff kann über das Netzwerk erfolgen. Es sind weder technische Details noch ein Exploit zur Schwachstelle bekannt. Es muss davon ausgegangen werden, dass ein Exploit zur Zeit etwa USD $2k-$5k kostet.

Es sind keine Informationen bezüglich Gegenmassnahmen bekannt. Der Einsatz eines alternativen Produkts bietet sich im Zweifelsfall an.

CVSSv3

CVSSv2

CPE

• cpe:/a:libtiff:libtiff:4.0.6

Exploiting

Gegenmassnahmen

Timeline

Quellen

Eintrag

Die Schwachstelle wurde am 28.10.2016 publik gemacht. Die Verwundbarkeit wird unter CVE-2016-8331 geführt. Der Angriff kann über das Netzwerk erfolgen. Es sind weder technische Details noch ein Exploit zur Schwachstelle bekannt. Es muss davon ausgegangen werden, dass ein Exploit zur Zeit etwa USD $2k-$5k kostet.

Es sind keine Informationen bezüglich Gegenmassnahmen bekannt. Der Einsatz eines alternativen Produkts bietet sich im Zweifelsfall an.

CVSSv3

CVSSv2

CPE

• cpe:/a:libtiff:libtiff:4.0.6

Exploiting

Gegenmassnahmen

Timeline

Quellen

Eintrag

scipID: 80179
Betroffen: Huawei VCN500
Veröffentlicht: 11.01.2016
Risiko: kritisch

Erstellt: 12.01.2016
Eintrag: 67.3% komplett

Beschreibung

In Huawei VCN500 wurde eine kritische Schwachstelle ausgemacht. Hierbei betrifft es eine unbekannte Funktion der Komponente Operation and Maintenance Unit. Dank der Manipulation mit einer unbekannten Eingabe kann eine schwache Authentisierung-Schwachstelle (Replay) ausgenutzt werden. Die Auswirkungen sind bekannt für Vertraulichkeit, Integrität und Verfügbarkeit.

Die Schwachstelle wurde am 11.01.2016 öffentlich gemacht. Die Verwundbarkeit wird als CVE-2015-8331 geführt. Der Angriff kann über das Netzwerk angegangen werden. Um eine Ausnutzung durchzusetzen, muss keine spezifische Authentisierung umgesetzt werden. Technische Details sind nicht bekannt und ein Exploit zur Schwachstelle ist ebenfalls nicht vorhanden.

CVSS

Base Score: 6.8 (CVSS2#AV:N/AC:M/Au:N/C:P/I:P/A:P) [?]
Temp Score: 5.9 (CVSS2#E:ND/RL:OF/RC:ND) [?]

CPE

• cpe:/a:huawei:vcn500

Exploiting

Klasse: Schwache Authentisierung
Lokal: Nein
Remote: Ja

Verfügbarkeit: Nein

Aktuelle Preisschätzung: $2k-$5k (0-day) / $0-$1k (Heute)

Gegenmassnahmen

Empfehlung: Upgrade
Status: Offizieller Fix
0-Day Time: 0 Tage seit gefunden

Upgrade: VCN500 V100R002C00SPC200

Timeline

11.01.2016 | Advisory veröffentlicht
12.01.2016 | VulDB Eintrag erstellt
12.01.2016 | VulDB Eintrag aktualisiert

Quellen

CVE: CVE-2015-8331 (mitre.org) (nvd.nist.org) (cvedetails.com)

scipID: 80179
Betroffen: Huawei VCN500
Veröffentlicht: 11.01.2016
Risiko: kritisch

Erstellt: 12.01.2016
Eintrag: 67.3% komplett

Beschreibung

In Huawei VCN500 wurde eine kritische Schwachstelle ausgemacht. Hierbei betrifft es eine unbekannte Funktion der Komponente Operation and Maintenance Unit. Dank der Manipulation mit einer unbekannten Eingabe kann eine schwache Authentisierung-Schwachstelle (Replay) ausgenutzt werden. Die Auswirkungen sind bekannt für Vertraulichkeit, Integrität und Verfügbarkeit.

Die Schwachstelle wurde am 11.01.2016 öffentlich gemacht. Die Verwundbarkeit wird als CVE-2015-8331 geführt. Der Angriff kann über das Netzwerk angegangen werden. Um eine Ausnutzung durchzusetzen, muss keine spezifische Authentisierung umgesetzt werden. Technische Details sind nicht bekannt und ein Exploit zur Schwachstelle ist ebenfalls nicht vorhanden.

CVSS

Base Score: 6.8 (CVSS2#AV:N/AC:M/Au:N/C:P/I:P/A:P) [?]
Temp Score: 5.9 (CVSS2#E:ND/RL:OF/RC:ND) [?]

CPE

• cpe:/a:huawei:vcn500

Exploiting

Klasse: Schwache Authentisierung
Lokal: Nein
Remote: Ja

Verfügbarkeit: Nein

Aktuelle Preisschätzung: $2k-$5k (0-day) / $0-$1k (Heute)

Gegenmassnahmen

Empfehlung: Upgrade
Status: Offizieller Fix
0-Day Time: 0 Tage seit gefunden

Upgrade: VCN500 V100R002C00SPC200

Timeline

11.01.2016 | Advisory veröffentlicht
12.01.2016 | VulDB Eintrag erstellt
12.01.2016 | VulDB Eintrag aktualisiert

Quellen

CVE: CVE-2015-8331 (mitre.org) (nvd.nist.org) (cvedetails.com)