Skip to content

Deserialisation Event Generation : vulnerability detection #395

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

lovesh-ap
Copy link
Contributor

No description provided.

AnupamJuniwal and others added 18 commits September 6, 2023 12:20
…ore information regarding deserialization attacks
…node only instead of a stack. This also contains changes to include information based on object being deserialized in a parent child, but in an adhoc format, this would be helpful for cases where events are triggered due to deserialization being done.
# Conflicts:
#	newrelic-security-agent/src/main/java/com/newrelic/agent/security/instrumentator/dispatcher/Dispatcher.java
#	newrelic-security-api/src/main/java/com/newrelic/api/agent/security/schema/AgentMetaData.java
#	newrelic-security-api/src/main/java/com/newrelic/api/agent/security/schema/VulnerabilityCaseType.java
#	settings.gradle
…erialisation_improvement_poc

# Conflicts:
#	gradle.properties
@lovesh-ap lovesh-ap self-assigned this Mar 12, 2025
@IshikaDawda IshikaDawda requested a review from k2himanshu April 23, 2025 09:10
@k2himanshu k2himanshu merged commit c1299e0 into feature/include-http-response Apr 23, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants