Alerts This Week
Warning Icon 1 692
Alerts This Week
Warning Icon 1 692

Gentoo: GLSA-202301-07 High: MyApp External Data Exposure Threat

gentoo
Calendar Grey May 26, 2017
Dist Gentoo Esm H88
Recent Teeworlds client security advisory highlights potential threats of unauthorized code execution. Suggested update to mitigate vulnerabilities.
Teeworlds client vulnerability in snap handling could result in execution of arbitrary code.

Summary

Teeworlds client contains a vulnerability allowing a malicious server to execute arbitrary code, or write to arbitrary physical memory via the CClient::ProcessServerPacket method.

Resolution

All Teeworlds users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=games-action/teeworlds-0.6.4:0"

References

[ 1 ] CVE-2016-9400 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9400

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201705-13
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: Teeworlds: Remote execution of arbitrary code on client
Date: May 26, 2017
Bugs: #600178
ID: 201705-13

Synopsis

Teeworlds client vulnerability in snap handling could result in execution of arbitrary code.

Background

Teeworlds is an online multi-player platform 2D shooter.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 games-action/teeworlds < 0.6.4 >= 0.6.4

Impact

===== A remote malicious server can write to arbitrary physical memory locations and possibly execute arbitrary if a vulnerable client joins the server.

Workaround

There is no known workaround at this time.

Related News

Your message here