«
Expand/Collapse
28 items tagged "spring"
Related tags:
spring framework [+],
hacks [+],
information [+],
use [+],
security constraints [+],
runasmanager [+],
predefined user [+],
login request [+],
location url [+],
invocation [+],
information disclosure vulnerability [+],
escalation [+],
acceptable use [+],
vulnerability [+],
service interface [+],
reverb [+],
path parameter [+],
path [+],
musical [+],
mapping requests [+],
malicious client [+],
class instances [+],
bugtraq [+],
arbitrary code execution [+],
vulnerabilities [+],
txt [+],
tripod [+],
tool [+],
time on his hands [+],
subscription customers [+],
strandbeest [+],
springsource [+],
spring reverb [+],
spring clamp [+],
spare time [+],
show [+],
server room [+],
security privilege [+],
safer use [+],
recording studio [+],
rainy day [+],
rainy [+],
privilege [+],
pete [+],
papercraft [+],
misc [+],
laser light show [+],
laser [+],
joe [+],
iphone [+],
information disclosure [+],
header [+],
hackers [+],
guitar signal [+],
guitar amplifiers [+],
guitar [+],
gear [+],
execution [+],
diy [+],
death row [+],
cve [+],
crims [+],
class classloader [+],
class [+],
bypass [+],
arbitrary code [+],
april showers bring may flowers [+],
security [+],
framework [+]
-
-
13:01
»
Hack a Day
Spring reverb is something we’re used to hearing about when it comes to guitar amplifiers. It’s a coil spring stretched the length of the amp’s housing. One end is fed the guitar signal, with a pickup at the other to capture the output. But this spring reverb is on a much grander scale. [Jochem van Grieken] strung up [...]
-
-
10:01
»
Hack a Day
If you’re running your own recording studio, you’re going to need a lot of gear that seems excessively esoteric to the non-musically inclined. A rack full of synth gear looks just like any other cabinet of technology you would find in a server room. Electronic music is, for the most part, very utilitarian looking, but [...]
-
-
9:11
»
Hack a Day
Admittedly this post is flirting with flamebait, but we think the concept of using a spring clamp as an iPhone tripod mount has a lot of hacking potential. Hear us out, and if we havn’t made our case you can rant about it in the comments. [Joe] wanted an easy way to mount his iPhone [...]
-
7:51
»
Packet Storm Security Advisories
Spring Security provides a mechanism (RunAsManager) to allow particular operations to run with a different set of privileges than the predefined user. The implementation contains a race condition whereby the escalated privileges could also be used in a different invocation in another thread. Versions 2.0.0 to 2.0.6 and 3.0.0 to 3.0.5 are affected.
-
7:51
»
Packet Storm Security Recent Files
Spring Security provides a mechanism (RunAsManager) to allow particular operations to run with a different set of privileges than the predefined user. The implementation contains a race condition whereby the escalated privileges could also be used in a different invocation in another thread. Versions 2.0.0 to 2.0.6 and 3.0.0 to 3.0.5 are affected.
-
7:51
»
Packet Storm Security Misc. Files
Spring Security provides a mechanism (RunAsManager) to allow particular operations to run with a different set of privileges than the predefined user. The implementation contains a race condition whereby the escalated privileges could also be used in a different invocation in another thread. Versions 2.0.0 to 2.0.6 and 3.0.0 to 3.0.5 are affected.
-
7:43
»
Packet Storm Security Advisories
Spring Framework versions 3.0.0 to 3.0.5 and Spring Security versions 2.0.0 to 2.0.6 and 3.0.0 to 3.0.5 suffer from serialization issues. Several issues have been reported which may affect applications which de-serialize objects from an untrusted source such as a remote client. It is possible for a malicious client to inject undesirable behavior into the server by serializing proxies rather than specific class instances, or by taking advantage of internal AOP interfaces which were being exposed through the remote service, in addition to the service interface.
-
7:43
»
Packet Storm Security Misc. Files
Spring Framework versions 3.0.0 to 3.0.5 and Spring Security versions 2.0.0 to 2.0.6 and 3.0.0 to 3.0.5 suffer from serialization issues. Several issues have been reported which may affect applications which de-serialize objects from an untrusted source such as a remote client. It is possible for a malicious client to inject undesirable behavior into the server by serializing proxies rather than specific class instances, or by taking advantage of internal AOP interfaces which were being exposed through the remote service, in addition to the service interface.
-
7:41
»
Packet Storm Security Exploits
Spring Security allows the use of a parameter (named "spring-security-redirect" by default) to determine the location URL to which a user will be redirected after logging in. This will normally be submitted as part of the login request, so is deemed to be an acceptable use of remote supplied data. However, the functionality is in a base class which is also shared by logout code, so a logout URL could be maliciously constructed to contain a version of this parameter which contained CRLF characters in order to inject additional headers or split the response. Versions 2.0.0 to 2.0.6 and 3.0.0 to 3.0.5 are affected.
-
7:41
»
Packet Storm Security Recent Files
Spring Security allows the use of a parameter (named "spring-security-redirect" by default) to determine the location URL to which a user will be redirected after logging in. This will normally be submitted as part of the login request, so is deemed to be an acceptable use of remote supplied data. However, the functionality is in a base class which is also shared by logout code, so a logout URL could be maliciously constructed to contain a version of this parameter which contained CRLF characters in order to inject additional headers or split the response. Versions 2.0.0 to 2.0.6 and 3.0.0 to 3.0.5 are affected.
-
7:41
»
Packet Storm Security Misc. Files
Spring Security allows the use of a parameter (named "spring-security-redirect" by default) to determine the location URL to which a user will be redirected after logging in. This will normally be submitted as part of the login request, so is deemed to be an acceptable use of remote supplied data. However, the functionality is in a base class which is also shared by logout code, so a logout URL could be maliciously constructed to contain a version of this parameter which contained CRLF characters in order to inject additional headers or split the response. Versions 2.0.0 to 2.0.6 and 3.0.0 to 3.0.5 are affected.
-
7:36
»
Packet Storm Security Advisories
Spring Framework versions 3.0.0 to 3.0.5, 2.5.0 to 2.5.6.SEC02, and 2.5.0 to 2.5.7.SR01 suffer from an information disclosure vulnerability.
-
-
17:27
»
Hack a Day
Here in the Midwest it sometimes seems like Spring will never, well…spring. We get that “April showers bring May flowers”, but nearly all of the last month has been cold and rainy around these parts. While things are improving, we think it’s always good practice to have a few fun projects at the ready, just [...]
-
-
12:29
»
Hack a Day
[Pete] had some spare time on his hands over his spring break, and he was itching to build something. He settled on a laser light show since, after all it was spring break, and what says “Party” better than a laser light show? He glued three hobby mirrors to three small motors, mounting the motor [...]
-
-
1:01
»
Packet Storm Security Recent Files
Spring Security does not consider URL path parameters when processing security constraints. By adding an URL path parameter to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification (see below). Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed.
-
1:01
»
Packet Storm Security Exploits
Spring Security does not consider URL path parameters when processing security constraints. By adding an URL path parameter to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification (see below). Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed.
-
-
18:35
»
SecuriTeam
An arbitrary code execution vulnerability was discovered in Springsource's Spring Framework..
-
Make your website safer. Use external penetration testing service. First report ready in one hour!
-
-
18:01
»
Packet Storm Security Advisories
Spring Framework suffers from an arbitrary code execution vulnerability. Versions affected include 3.0.0 to 3.0.2, 2.5.0 to 2.5.6SEC01 (community releases) and 2.5.0 to 2.5.7 (subscription customers).
0day.today (was: 1337day, Inj3ct0r, 1337db)
OSVDB Vulnerabilities
Exploit-DB
SecurityFocus Vulnerabilities
Bugtraq
XSSed
Sophos security news
Penetration Testing
BackTrack Linux Forums
Threatpost
SecDocs
carnal0wnage.attackresearch.com
Carnal0wnage
Darknet
The Exploitant
Wirevolution