0day.today - Biggest Exploit Database in the World.
Things you should know about 0day.today:
Administration of this site uses the official contacts. Beware of impostors!
- We use one main domain: http://0day.today
- Most of the materials is completely FREE
- If you want to purchase the exploit / get V.I.P. access or pay for any other service,
you need to buy or earn GOLD
Administration of this site uses the official contacts. Beware of impostors!
We DO NOT use Telegram or any messengers / social networks!
Please, beware of scammers!
Please, beware of scammers!
- Read the [ agreement ]
- Read the [ Submit ] rules
- Visit the [ faq ] page
- [ Register ] profile
- Get [ GOLD ]
- If you want to [ sell ]
- If you want to [ buy ]
- If you lost [ Account ]
- Any questions [ admin@0day.today ]
- Authorisation page
- Registration page
- Restore account page
- FAQ page
- Contacts page
- Publishing rules
- Agreement page
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Scala 2.x Privilege Escalation Vulnerability
Author
Risk
[
Security Risk High
]0day-ID
Category
Date add
CVE
Platform
A privilege escalation vulnerability has been identified in the Scala compilation daemon. The compile daemon is started explicitly by the `fsc` command, or implicitly by executing a Scala source file as a script (e.g `scala MyScript.scala`). Note: Using the `scala` command to start a REPL or to run a pre-compiled class does not start the compile daemon. # Impact While the compile daemon is running, an attacker with local access to the machine can execute code as the user that started the compile daemon, and can write arbitrary class files to any location on the filesystem that the user has access to. # Affected Versions - Scala 2.1.6-2.10.6; 2.11.0-2.11.11; 2.12.0-2.12.3 # Mitigation - Use `scala -nocompdaemon MyScript.scala` rather than `scala MyScript.scala` to disable the implicit startup and use of the daemon. - Avoid explicitly starting `fsc` - Upgrade to Scala 2.10.7 2.11.12, 2.12.4 or higher which restricts the sensitive file to be readable only by the owner. These releases also change the location of the sensitive file: it is written in the directory `$HOME/.scalac`. Announcement: http://scala-lang.org/news/security-update-nov17.html Scala Downloads: http://scala-lang.org/download/ # 0day.today [2024-11-16] #