Cool Solutions

How to Use FILTCFG to Protect Against Possible Security Vulnerability with ApacheAdmin on NetWare 6.5


January 29, 2009 5:22 pm





TID 7001907 gives details about a potential security vulnerability with Apache, or more specifically ApacheAdmin, on NetWare 6.5 after you’ve installed an OES2 Linux server into the same tree.

However there seems to (currently) be some ambiguity about the actual cause and suggested fix.

Here’s one way of securing access to port 2200 on your NetWare server using FILTCFG.

  1. edit sys:/etc/builtins.cfg and add the following line (perhaps before IPX services are defined)
  2. PROTOCOL-SERVICE IP, NWWebMgr, pid=TCP port=2200 srcport=<All>, NetWare Web Manager
  3. load INETCFG and navigate to Protocols | TCP/IP
  4. change Filter Support to Enabled
  5. load FILTCFG and navigate to Configure TCP/IP Filters | Define TCP/IP filters | Packet Forwarding Filters
  6. change Status to Enabled
  7. press [Ins] twice on Filters to add the following filter
  8. Packet Type: NWWebMgr
  9. press [Esc] and select Yes when prompted to Save Filter?
  10. press [Ins] twice on Exceptions to add the following exception
  11. Packet Type: NWWebMgr
    Src Addr Type: Network
    Src IP Address: network/netmask
  12. press [Esc] and select Yes when prompted to Save Filter?
  13. press [Esc] four times and select Yes when prompted to Exit FILTCFG?
  14. RESTART SERVER (unfortunately – to re-read builtins.cfg)
1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5 (1 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.


  1. By:davidkrotil

    From same TID

    The fix to this issue is to apply support pack 8 to the server.

  2. By:ecyoung

    Yeah, what happened with SP8? I encountered another “published” fix that wasn’t fixed just the other day: “260382 SCRSAVER – req for emergency password stored locally in an ecrypted file” was not included, even though it was published.