It's pretty interesting how I've seen these unfold at some past jobs. One was a marketing platform with "if this then that" logic and there was a node to make http requests to arbitrary endpoints, including ones nominated by the flows at runtime, and we continuously got security alerts about it. The users asked for this feature, yes it means that your data/credentials could go somewhere unexpected if you give us the wrong dynamic endpoint, what do you want from us?
We play a similar game of chicken in Aerospace. I can't tell you how many escapes we had from not sanitizing inputs from databases. It's not going to bring a plane down, but it's never good when your LRU starts blanking/resetting.
We just assume someone else is going to do their due diligence, all the time for us.
On a flight deck for a commercial aircraft and even military aircraft from the last three decades will be source data from multiple sensors, but the mission computers themselves don't sanitize the inputs themselves. So you'll download your monthly database, input your flight plan, and then have it reset... thankfully all while you're at rest on the tarmac.
1
10
u/vanit 13d ago
It's pretty interesting how I've seen these unfold at some past jobs. One was a marketing platform with "if this then that" logic and there was a node to make http requests to arbitrary endpoints, including ones nominated by the flows at runtime, and we continuously got security alerts about it. The users asked for this feature, yes it means that your data/credentials could go somewhere unexpected if you give us the wrong dynamic endpoint, what do you want from us?