6 matches found
wahlen.kreis-nea.de Cross Site Scripting vulnerability OBB-3705848
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
nea-edicoes.com Cross Site Scripting vulnerability OBB-3465017
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
nea-tech.it Cross Site Scripting vulnerability OBB-3287525
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
nea-nederland.nl Cross Site Scripting vulnerability OBB-3070769
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
nea-edicoes.com Cross Site Scripting vulnerability OBB-2660057
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
Unexpected file removal from datastore after failed NEA deployment
Challenge After a failed attempt to deploy NEA for tenants on the provider's side, all files from the datastore root folder including VM files are deleted. Cause This issue is caused by using only the " " space symbol for the NEA name and the deployment has failed. Veeam tries to detect failed NE...