Modify ↓
#21732 closed task (duplicate)
JOSM affected to Log4J-security-issue??
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Plugin | Version: | |
| Keywords: | log4j cve | Cc: |
Description
Dear developers,
since the Log4Shell log4j vulnerability (CVE-2021-44228 / CVE-2021-45046) - cheat-sheet, my company is checking every Java-Software and wants to get a statement from the developer if there could be a security risk.
Can you tell me, if JOSM is affected to the log4J security issue?
Regards Marc
Attachments (0)
Change History (2)
comment:1 by , 4 years ago
| Component: | Core → Plugin |
|---|---|
| Keywords: | log4j cve added |
| Resolution: | → duplicate |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.



Closed as duplicate of #21657.
It was always only a bug in the plugin and not within JOSM core. The plugin was update. Any more questions?