frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: Fedijar – The Search Mastodon servers meant to have

https://fedijar.com
1•saneefansari•1m ago•0 comments

Show HN: Aitho – slides that advance when you say the words, not when you click

https://present.aitho.app/try
1•aumar2•4m ago•0 comments

Are you clinging to the TUI to feel like a developer?

1•TomEleff•6m ago•0 comments

Ask HN: Could AI's RH proof have used human work found in its training data?

1•nomilk•6m ago•0 comments

Vector and Similarity Search, by Hand

https://www.huy.rocks/everyday/11-21-2026-math-linear-algebra-notes-vector-and-similarity-search-...
1•huydotnet•6m ago•0 comments

Nospeaker: Make your MacBook's trackpad talk using its haptic motor

https://github.com/os6/nospeaker
1•vikrum•7m ago•0 comments

Tor Community Fellowship

https://forum.torproject.org/t/call-for-applications-tor-community-fellowship/22490
1•farhan291•7m ago•0 comments

When services fail, we see what they are made of

https://good.services/writing/when-services-fail-we-see-what-they-are-made-of
1•adrianhoward•7m ago•0 comments

Show HN: Exploitwatch – Alerts for vulnerable Docker containers (e.g. PHP2Shell)

https://github.com/marioleal/exploitwatch
1•ympb121•8m ago•1 comments

Inside an AI prophet's secretive visions for humanity's future

https://www.washingtonpost.com/technology/2026/11/22/inside-an-ai-prophets-secretive-plans-humani...
1•pretext•9m ago•0 comments

Ask HN: Why do these LLM models seem to improve like clockwork over time?

2•iknownthing•13m ago•2 comments

Liseur: Android ePub Reader

https://github.com/chmouel/liseur
1•swapnilmj•13m ago•1 comments

Enrico Fermi Doesn't Blow Up Chicago

https://colab.research.google.com/drive/1LNey4n-V8QciZLhcUSR7IUOKeId_58KP?usp=sharing
1•Eridanus2•13m ago•1 comments

A fast image processing library with low memory needs

https://github.com/libvips/libvips
1•SweetSoftPillow•13m ago•0 comments

Cybermacs 3D Window Manager

https://kibotronics.net/projects/cybermacs/
1•Kiboneu•15m ago•0 comments

Show HN: GTA6 Wiki – Reference Site for Grand Theft Auto VI

https://gtaviwiki.org/
1•ludydev•15m ago•0 comments

Apple says it will shut down its Apple Support Community forums after 28 years

https://mashable.com/tech/apple-shutting-down-support-community-forums
2•taubek•16m ago•0 comments

Perplexity and Intelligence

https://openai.com/index/perplexity-and-intelligence/
3•acossta•20m ago•1 comments

Software Rendering the Mandelbrot Fractal in Rust

https://antr.dev/blog/software-rendering-the-mandelbrot-fractal-in-rust/
1•lr0•22m ago•0 comments

Show HN: TEB RUN – a pseudo-3D arcade racer in TypeScript and Canvas, no engine

https://tebrun.io/
2•tebrun•23m ago•0 comments

Saving Lives Before the Singularity

https://clattubato.substack.com/p/saving-lives-before-the-singularity
1•paulpauper•23m ago•0 comments

Show HN: Type prompts directly in terminal shell to kickoff Claude and codex

https://github.com/mquan/llmao
1•quan•23m ago•0 comments

Banning RSI Is Mere Stalling

https://emethirsch.neocities.org/banning-rsi-is-mere-stalling
2•paulpauper•24m ago•0 comments

Boring: An Idiot in Berkeley

https://henryaj.substack.com/p/boring
1•paulpauper•24m ago•0 comments

How to make Three.js support real-time path tracing?

1•winstongu20•25m ago•0 comments

The Riemann Hypothesis (Post by Marty Ross of Mathologer)

https://mathematicalcrap.com/2026/11/22/the-riemann-hypothesis/
1•joebig•25m ago•0 comments

Connectome for Drones

https://huggingface.co/SingularityEdge/FlyDrone-SNN
1•janmirank•25m ago•0 comments

Proving Rust Web Application Correctness with Lean 4

https://www.reddit.com/r/rust/comments/1wz7q4o/proving_rust_web_application_correctness_with/
1•syumei•26m ago•0 comments

Amazon nearing $7.5B deal to buy AI startup Decart: FT

https://seekingalpha.com/news/4675396-amazon-nears-75b-deal-buy-ai-start-up-decart
1•rainhacker•27m ago•0 comments

The Quality Is Still on Me

https://edisoncode.com/articles/the-quality-is-still-on-me/
1•jeddawson•27m ago•0 comments
Open in hackernews

CRLF Injection in `–proxy-header` allows extra HTTP headers (CWE-93)

https://hackerone.com/reports/3133379
11•oblivionsage•1y ago

Comments

blueflow•1y ago
Check the man-page first. You need to know how a program is supposed to behave before you can know that an observed behavior is off-spec and warrants a bug.
robertlagrant•1y ago
I don't understand the "This is not supposed to happen". Can someone explain?

To me this is the same as

  --proxy-header "X-Test: hello" --proxy-header "X-Evil: owned"
flotzam•1y ago
Imagine running

  curl --proxy-header "X-Test: $UNTRUSTED_USER_INPUT"
wang_li•1y ago
That is not a bug in curl, at most it's a bug in whatever gathered $UNTRUSTED_USER_INPUT.
flotzam•1y ago
People still expect an API to reject illegal values. Calling the parameter --proxy-header (singular) could lead someone to assume that multiline strings are illegal values, even if there's a note in the docs somewhere saying otherwise.
blueflow•1y ago
Then the people assuming random things without doing research are to blame, not curl.
flotzam•1y ago
Apportioning blame doesn't get rid of bugs; misuse resistant APIs do.
blueflow•1y ago
Reading docs ("research") is essential part of engineering.

Lets ask the question reversed: How did people know in the first place what kind of string they need to give to --proxy-header?

flotzam•1y ago
> Reading docs ("research") is essential part of engineering.

Sure, but so is safety engineering. Making mechanisms more obvious to use correctly or fail safe if used incorrectly improves outcomes when flawed human beings use them. It also makes them more pleasant to use in general.

Besides, look at the man page in question. It's talking about this in terms of encoding niceties and doesn't even spell out the possibility of deliberate, let alone malicious multiline values:

"curl makes sure that each header you add/replace is sent with the proper end-of-line marker, you should thus not add that as a part of the header content: do not add newlines or carriage returns, they only mess things up for you."

That's inducing a wrong/incomplete mental model of how this parameter works.

jeroenhd•1y ago
I suppose it kind of depends. I agree with the curl team here that this is a case of garbage in/garbage out, but I can imagine this going wrong with a binary protocol like HTTP2 on the front and a text protocol like HTTP 1.1 behind a reverse proxy. The \r\n will make it to the proxy as a separate header, but will be turned into two headers on the upstream.

That said, this would be a (reverse) proxy vulnerability, not one in curl.

ale42•1y ago
I'm not sure where is the security issue here. As already noted, one can just put several --proxy-header arguments, so the functionality is equivalent.

The only way this would do something unexpected (and not necessarily dangerous besides breaking the service) would be if the curl command would be used in a scenario like: (1) curl is used by some script to access some API or other URL, (2) a user can configure the script to give a specific value to an header, let's say an authentication token or similar, but the user can't directly alter the curl command (e.g. because they can only change URL and TOKEN with a web interface). Here the user would be able to add an header IF the script is not properly sanitizing the input (so the supposed security issue IMHO would be in the script), but if adding an additional header breaks security, the underlying system has a problem too...

In a very far-stretched scenario, one can possibly add two CRLFs and have the rest of the header (if any) considered by the server as data. IF the request is a POST/PUT/... request, and IF the server returns (or allows later access to) the data, and IF the attacker manipulating the supposedly-restricted single-header can see the output of the call (or retrieve the saved data), then we'd have an information disclosure issue. Would it disclose anything sensitive? Not sure, unless there's an auth token or something AFTER the header. And again, I'd rather incriminate the curl caller for not sanitizing the input if this happens.

blueflow•1y ago
> doesn't even spell out the possibility of deliberate, ... multiline values

It does for me, as any kind of extra newlines results in a multi-line string.

> ... malicious ...

Like Daniel said, garbage in, garbage out. If you pass user inputs to curl, one should check what curl does with these values and take proper care.

robertlagrant•1y ago
> do not add newlines or carriage returns, they only mess things up for you

I disagree, but I would say that curl might as well add this as a validation check than a documentation warning.

blueflow•1y ago
This is explained in the ticket:

  One of the reasons we still allow that is that this "feature" was used quite deliberately by users in the past and I have hesitated to change that for the risk that it will break some users use cases.
robertlagrant•1y ago
Yes, I'm not sure if I agree with this or not. Those users don't have to upgrade. But obviously I'm not maintaining a key tool for the world. It's just my opinion.
soraminazuki•1y ago
One shouldn't construct shell commands from untrusted user input in the first place unless they know exactly what they're doing and is aware of all the pitfalls. It's the worst possible tool to be using if the aim is to avoid security issues with minimal effort. Debating about this particular curl quirk distracts from the bigger issue IMO.
robertlagrant•1y ago
> That is not a bug in curl, at most it's a bug in whatever gathered $UNTRUSTED_USER_INPUT.

But that could just contain the bad header only, could it not?