WS-Attacker | modular framework for web services penetration | Security Testing library

by RUB-NDS Java Version: v1.8 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | WS-Attacker Summary

WS-Attacker is a Java library typically used in Testing, Security Testing applications. WS-Attacker has no bugs, it has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

WS-Attacker is a modular framework for web services penetration testing. It is developed by the Chair of Network and Data Security, Ruhr University Bochum () and the Hackmanit GmbH (

Support

Quality

Security

License

Reuse

Support

WS-Attacker has a low active ecosystem.

It has 443 star(s) with 125 fork(s). There are 33 watchers for this library.

It had no major release in the last 12 months.

There are 17 open issues and 6 have been closed. On average issues are closed in 57 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of WS-Attacker is v1.8

Quality

WS-Attacker has 0 bugs and 0 code smells.

Security

WS-Attacker has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

WS-Attacker code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

WS-Attacker is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

WS-Attacker releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

WS-Attacker saves you 56141 person hours of effort in developing the same functionality from scratch.

It has 64492 lines of code, 4299 functions and 662 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed WS-Attacker and discovered the below as its top functions. This is intended to give you an instant insight into WS-Attacker implemented functionality, and help decide if they suit your requirements.

Initialize the form components
Sets the signature wrapping element
Initialize the text field text fields
Sets the text of encrypted elements
Initialize the components
Init the table
Checks if the user has an attack configuration
Set the state of this button
Initialize the form
Generate a message with an envelope
Updates the state of the state machine
Called when the plugin is active
This method is invoked when a wrapper element is being wrapped
Generate a tampered request
Initialize the filters
Override this method to hook the implementation
Updates state of the state machine
Get the hash value for a string
Create a tampered request
We don t need to do this
We need to modify the soapaction implementation
Update the attack model
Generate collision table
This method should only be called once
Method to get a tampered request
We have an attack implementation

Get all kandi verified functions for this library.

WS-Attacker Key Features

No Key Features are available at this moment for WS-Attacker.

WS-Attacker Examples and Code Snippets

No Code Snippets are available at this moment for WS-Attacker.

Community Discussions

Trending Discussions on WS-Attacker

Why are Android versions older than 5.0 not vulnerable to CVE-2017-13156?

QUESTION

Why are Android versions older than 5.0 not vulnerable to CVE-2017-13156?

Asked 2020-Jan-28 at 09:46

I was just reading about the Janus vulnerability (CVE-2017-13156) and there is one thing I cannot understand.

The vulnerability lies in the implementation of the installation of the APK and Signature Scheme v1 (JAR signature). It allows you to craft a mallicious APK file by prepending a mallicious DEX file to a legitimate APK. The mallicious DEX file is installed instead of the DEX file of the legitimate APK. The signature (if using v1 scheme) is not broken.

The writeup in the link above mentions the vulnerable versions of Android being 5.0 and newer (the CVE record mentions 5.1.1 to 8.0, but that's not the main problem now).

So my question is:

Why is 5.0 the lowest vulnerable version of Android? Does Android older than 5.0 use a different signature scheme? Or is there a difference in the way APKs are being installed on Android 5.0 and newer and Android lower than 5.0?

...

ANSWER

Answered 2020-Jan-28 at 09:46

ART, the Android Runtime replaced the Dalvik VM since Android 5.0.

And obviously, an ART exploit does not apply to the Dalvik VM.

Source https://stackoverflow.com/questions/59945800

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install WS-Attacker

You can download it from GitHub.
You can use WS-Attacker like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the WS-Attacker component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: