T-015: InstallShield / Macrovision / Acresso FLEXnet Connect Vulnerabilities

Tags

Special Forums Cybersecurity Security Advisories (RSS) T-015: InstallShield / Macrovision / Acresso FLEXnet Connect Vulnerabilities

11-13-2008

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

T-015: InstallShield / Macrovision / Acresso FLEXnet Connect Vulnerabilities

Acresso FLEXnet Connect executes scripts that are insecurely retrieved from a remote web server, which can allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system. The risk is MEDIUM. By modifying the rule script that is sent to a FLEXnet Connect client, a remote unauthenticated attacker may be able to execute arbitrary code on a vulnerable system.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. HP-UX

installshield....

hi all is it possible to automate installaion process of any software on unix? for eg. we have our front end on windows and we have installshield package that installs everything creating folder structure to creating database. now we are planning to automate our backend installation like...

2. Solaris

some questions on 310-015

hi can any1 pls ans these questions 22. Which two statements about the functionality of the syslogd daemon are true? (Choose two) A. Error messages can only be logged locally in a system log. B. The kernel, daemons, and syslogd each write directly to a system log. C. Syslogd can write...

LEARN ABOUT DEBIAN

fluxbox-remote

FLUXBOX-REMOTE(1)						  Fluxbox Manual						 FLUXBOX-REMOTE(1)

NAME

       fluxbox-remote - command line access to key commands for fluxbox(1)

SYNOPSIS

       fluxbox-remote command

DESCRIPTION

       fluxbox-remote(1) is designed to allow scripts to execute most key commands from fluxbox(1). fluxbox-remote(1) will only work with
       fluxbox(1): its communications with fluxbox(1) are not standardized in any way. It is recommended that a standards-based tool such as
       wmctrl(1) be used whenever possible, in order for scripts to work with other window managers.

CAVEATS

       fluxbox-remote(1) uses the X11 protocol to communicate with fluxbox(1). Therefore, it is possible for any user with access to the X(7)
       server to use fluxbox-remote(1). For this reason, several key commands have been disabled. Users should be aware of the security
       implications when enabling fluxbox-remote(1), especially when using a forwarded X(7) connection.

RESOURCES

       session.screen0.allowRemoteActions: <boolean>
	   This resource in ~/.fluxbox/init must be set to 'true' in order for fluxbox-remote(1) to function. Please read the CAVEATS first.

ENVIRONMENT

       In order to communicate with fluxbox(1), the DISPLAY environment variable must be set properly. Usually, the value should be ':0.0'.

AUTHORS

       This man page written by Mark Tiefenbruck <mark at fluxbox.org>

SEE ALSO

       fluxbox(1) fluxbox-keys(5) wmctrl(1)

AUTHOR

       Mark Tiefenbruck <mark@fluxbox.org>
	   Author.

fluxbox-remote.txt						 27 February 2011						 FLUXBOX-REMOTE(1)

Security Advisories (RSS)