-
Notifications
You must be signed in to change notification settings - Fork 634
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
[Rust] List of OIDs which cause server crashes #1748
Comments
Which feed are you using? |
These OIDs I've extracted from the greenbone "discovery" list. "Feed"... I guess you're talking SCAP vs whatever the other one is? Not sure... This?
|
Ah, so you're sending those OIDs? Got it. I misunderstood, thinking that openvasd returns these OIDs when calling /vts, then crashes. The JSON is invalid—the last comma before However, openvasd shouldn't crash because of that. Could you provide the entire JSON you're sending and the endpoint it’s being sent to, so I can replicate the crash? Any sensitive information can be replaced with '*******' or similar placeholders. |
Which then comes in as
|
I probably won't be back on this stuff until next Monday, but might have noticed a commonality. Seems a lot of these Will look into what the XML contains... Must be the NMAP response has a string somewhere a number is expected. |
ah ok, so openvasd doesn't crash based on the provided input but when starting it creates the behavior described in 1744? |
Yeah when it gets to specific OIDs. Think the sequence is:
I have seen |
Thanks for providing the oids. This should be fixed with the fixes for #1744. |
Nice one. Week got busy. I'll cycle back next week. |
Seems a lot involve
803***
and104***
.The text was updated successfully, but these errors were encountered: