apache / apache/arrow-java

[Java] FuzzIpcStream: Uncaught exception in org.apache.arrow.memory.BaseAllocator.buffer

Ouverte
#354 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Type: bug
Langage dominant
Java
Étoiles
94
Forks
152
Merge moyen
3 j 16 h
PR mergées (30 j)
11

Description

Detailed Report: https://oss-fuzz.com/testcase?key=6427573486223360

Project: arrow-java
Fuzzing Engine: libFuzzer
Fuzz Target: FuzzIpcStream
Job Type: libfuzzer_asan_arrow-java
Platform Id: linux

Crash Type: Uncaught exception
Crash Address:
Crash State:
org.apache.arrow.memory.BaseAllocator.buffer
org.apache.arrow.memory.RootAllocator.buffer
org.apache.arrow.memory.BaseAllocator.buffer

Sanitizer: address (ASAN)

Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_arrow-java&revision=202201310606

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6427573486223360

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
When you fix this bug, please
- mention the fix revision(s).
- state whether the bug was a short-lived regression or an old bug in any stable releases.
- add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.

This bug is subject to a 90 day disclosure deadline. If 90 days elapse
without an upstream patch, then the bug report will automatically
become visible to the public.

**Reporter**: [Liya Fan](https://issues.apache.org/jira/browse/ARROW-15561) / @liyafan82

**Note**: *This issue was originally created as [ARROW-15561](https://issues.apache.org/jira/browse/ARROW-15561). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par suivre les instructions de reproduction d’OSS-Fuzz pour la cible FuzzIpcStream et le testcase associé, puis examinez la stack trace de BaseAllocator.buffer. Le payload ne nomme aucun fichier source ni aucun test ; le travail est terminé lorsque l’exception non interceptée est reproduite et qu’il est vérifié que le correctif upstream l’empêche.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
java
Domaine
data-engineering
Type d'issue
Bug
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
20/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.